Fetch JSON Results

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

No annotations provided, so description carries full burden. It discloses potential large response and that it returns results directly in MCP response. Lacks specifics on error handling or authentication, but adequately covers key behavior.

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?

Three sentences, front-loaded with verb, no wasted words. Each sentence adds distinct value: purpose, usage caveat, alternatives, and post-step.

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?

Given complexity (3 params, output schema), description fully covers what the tool does, when to use it, alternatives, and follow-up actions. No gaps identified.

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?

Schema coverage is 100% with descriptions for all parameters. Description adds no additional meaning beyond schema. Baseline score of 3 is appropriate as schema already documents parameter purposes.

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?

Description clearly states it fetches JSON results for Suparse document IDs directly in MCP response. It specifies the resource (Suparse documents), action (fetch JSON), and distinguishes from siblings like download_results for other formats and delete_documents for cleanup.

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?

Explicitly advises when to use ('only when you need the full JSON in context'), provides alternatives ('use download_results for CSV, XLSX, etc.'), and suggests post-step ('call delete_documents after this tool succeeds'). Complete usage guidance.

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