get_document

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

Without annotations, the description carries the burden of disclosing behavior. It correctly indicates a read-only operation ('get'), but it does not mention potential errors (e.g., 404 if ID not found), authorization requirements, or rate limits. The phrase 'full content and metadata' is somewhat vague but adequate for a simple retrieval tool.

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?

The description is a single sentence that is direct and free of extraneous words. Every word contributes to defining the tool's purpose.

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?

For a simple single-parameter retrieval tool with no output schema or annotations, the description adequately covers purpose and return type (full content and metadata). It does not describe the output structure but given the low complexity, this is acceptable.

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% (the only parameter 'id' is fully described in the schema). The description adds no additional meaning beyond 'by ID', which echoes the schema. Baseline 3 is appropriate as the schema already handles semantic load.

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?

The description clearly states the verb 'Get', the resource 'document', and the qualifier 'by ID', differentiating it from sibling tools like search_documents (which searches across documents) and update_document (which modifies). It specifies 'full content and metadata', giving a precise purpose.

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?

The description implies usage when you have a specific document ID and need its complete data, but it does not explicitly state when this tool should be used over alternatives, nor does it mention restrictions or prerequisites beyond having an ID.

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