Get doc

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It conveys that the operation is a read (fetching full content), but it does not describe error handling, authentication requirements, rate limits, or what happens for invalid IDs. For a simple read operation, this is adequate but not exhaustive.

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, tightly-packed sentence with no filler. It front-loads the core purpose ('Fetch the full content of a doc by id') and then adds the source context. Every word earns its place.

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 tool with a single parameter and no output schema, the description is complete enough. It specifies the resource, the parameter's provenance, and the action. Given the low complexity, nothing critical is missing for an agent to call it correctly.

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 only defines 'id' as a required string with no description. The tool description adds critical semantic context by specifying that the id comes from search_docs results, which tells the agent how to obtain a valid id. This goes beyond what the schema alone provides.

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 tool's function: fetching the full content of a doc by id. It explicitly ties the id source to search_docs results, which distinguishes it from other sibling tools like get_task or search_docs itself. The verb 'Fetch' and resource 'doc' are specific and unambiguous.

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 a usage context by saying 'from search_docs results,' suggesting it is a follow-up operation. However, it does not explicitly state when to use this tool vs. alternatives, nor does it mention any exclusions. The guidance is implicit rather than explicit, leaving the agent to infer the intended workflow.

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