fetch

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

No annotations, so description carries full burden. It states returns full document text with metadata and lists return fields. Implies safe read operation, but could disclose potential costs or limits. Still, adequate transparency.

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?

Well-structured with headers (usage, parameters, returns). Front-loaded with purpose. A bit verbose but every sentence adds value. Minor redundancy could be trimmed.

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?

Simple 1-param tool with output schema. Description covers workflow, parameter usage, and return fields. Nothing missing.

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 already has 100% coverage with description and examples. Description adds crucial context: ID must come from search results and be exact. Adds meaning beyond schema.

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 'Retrieves the full content of a document from search results.' The verb 'fetch' and resource 'full content of a document' are specific. Distinguishes from sibling 'search' by outlining the workflow: use search first, then fetch.

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?

Explicit usage instructions provided: '1. First use search() to find relevant documents, 2. Use the 'id' from search results to fetch full content.' Also emphasizes using exact IDs. Clearly guides when to use and implies prerequisite.

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