Documentation MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, description carries burden but only states it 'creates' a PDF; lacks critical details like return type (bytes vs URL), idempotency, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise two-sentence structure with clear front-loading; every clause adds specific value about output features.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequately covers input parameters but incomplete due to missing output specification (critical gap since no output schema exists to explain what the tool returns).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Elevates above 100% schema coverage by elaborating that 'confidentiality markings' specifically means watermarks, headers, and footers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it generates a PDF documentation release and distinguishes from retrieval-focused siblings by emphasizing PDF creation with formatting features.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use versus alternatives (e.g., when to generate PDF vs. using get_document for online viewing).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.