get_document

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

No annotations are provided, so the description carries the full burden. It mentions the doc_id format and source, but does not explicitly state that the operation is read-only, nor disclose error behavior, permissions, or side effects. The name 'get' implies safety, but the description lacks explicit behavioral disclosure, though this is a minor issue for such 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 concise and well-structured: a clear purpose sentence, a usage sentence, and an args block with an example. Every sentence earns its place with no unnecessary repetition or fluff.

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 one-parameter get tool with an output schema, the description gives all necessary context for selection and invocation: how to get the ID, when to use it, and what it returns. It could mention error handling or limitations, but such details are not critical given the tool's simplicity and the presence of an output schema.

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?

The schema has no descriptions for the single parameter doc_id (0% coverage). The description compensates by explaining that it is the 'Document ID from search results' and gives a concrete example, providing the agent with sufficient understanding of what to pass.

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 states 'Get full document content by document ID' with a specific verb and resource. It further distinguishes from siblings by tying usage to search results ('after finding it via search_docs') and clarifying that the doc_id originates from search results, which differentiates it from tools like download_doc.

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 says 'Use this to retrieve the complete content of a document after finding it via search_docs,' giving a clear when-to-use context. It does not list when-not-to-use or alternatives, but the context is unambiguous enough for an agent to select it appropriately.

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