document_get

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

No annotations are provided, so the description is the sole behavioral source. It mentions the capability requirement, but it doesn't disclose error behavior (e.g., 404 on missing slug), return format, or side effects. 'Read' implies non-mutating, but this isn't explicit or elaborated.

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, front-loaded with the action, and every word contributes meaning. It is appropriately concise for a simple tool, though it borders on under-specified.

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?

Given the lack of annotations and output schema, and only one parameter, the description is incomplete. It doesn't explain the slug parameter, error handling, or how to handle the capability prerequisite. A more complete description would include these details to ensure confident invocation.

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 a single required parameter 'slug' with no description, and the tool description makes no mention of it. With 0% schema coverage and no parameter explanation, the agent must guess that slug identifies the document. The description adds no semantic value beyond the bare 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?

The description clearly states the tool reads a document, using a specific verb and resource. It implicitly distinguishes from sibling tools like document_search and document_list, which handle discovery rather than retrieval. However, it doesn't specify that it retrieves a single document by slug, leaving a slight gap.

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 provides a prerequisite ('when the optional document capability is installed') but no guidance on when to choose this tool over alternatives such as document_search or document_list. It doesn't contrast with siblings or explain what to do if the capability isn't present, leaving the agent without clear selection criteria.

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