[Positioning] PM Decision — AI/agent-first framing

Decision needed

Is the server explicitly AI/agent-first, or general-purpose?

Why this matters

Resolves several second-order questions:

• Why aren't there more tools? → Because more tools degrade agent selection accuracy.
• Why doesn't it support X feature? → Because we curate for agent use, not API coverage.
• How do I extend it? → Write a skill, not a fork.

Recommendation

Yes, AI/agent-first. The MCP server is the API surface for LLM agents talking to DocumentDB. Skills + agents are the application layer on top. This aligns with:

• The MCP ecosystem direction.
• The existence of documentdb-agent-kit.
• The deliberate tool consolidation (~18 tools, not 40).

Acceptance criteria

• Decision documented.
• README framed as "agent-first" in the lede.
• Tools-catalog page references the consolidation principle.
• Extensibility doc points users to skills, not forks.

Blocks

• Tools catalog page (Tier 2 DX).
• Positioning statement.
• Comparison table.