get_document

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

With no annotations provided, the description must convey behavioral traits. The verb 'Fetch' implies a read-only, non-destructive operation. However, it does not explicitly state that it is safe, describe any side effects, auth requirements, or error conditions. The existence of an output schema partially compensates, but more transparency would be beneficial.

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, self-contained sentence of 7 words. It is front-loaded with the action and resource, and every word earns its place. No fluff or redundancy.

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 retrieval tool with two parameters and an output schema, the description covers the core functionality adequately. The existence of sibling search tools is noted implicitly by specifying 'single Document.' However, it could briefly mention that this is the precise identifier-based counterpart to the fuzzy search tools.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema: it merely restates that the tool fetches by slug and kind. The schema already documents kind's possible values and slug's format adequately.

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 'Fetch a single Document by slug+kind.' clearly states the verb (Fetch), resource (Document), and method (by slug+kind). It immediately distinguishes from sibling tools like search_documents (which lists) and download_document_file (downloads a file), making the purpose 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 usage when you have a specific slug and kind to retrieve a single document, contrasting with search tools for fuzzy or list queries. However, it does not explicitly state when not to use it or mention alternatives like search_documents, which would improve guidance.

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