Read a document

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to restate safety. It adds that the tool returns 'full contents,' which is useful behavioral detail, but it does not elaborate on potential limitations (e.g., large documents, exact response structure), meaning it provides only marginal transparency beyond the annotations.

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, short sentence that front-loads the most important information: it returns full contents of one document. Every word earns its place, with no filler or redundant detail.

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 tool with a read-only annotation, the description is sufficient: it states what is returned (full contents) and the document scope (one document). The lack of an output schema is mitigated by the phrase 'full contents.' It does not discuss errors or prerequisites, but those are not critical given the tool's simplicity and the schema's clarity.

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%, and the parameter 'slug' is already described as 'Document slug from list_documents,' which fully explains its meaning. The description contributes no additional parameter semantics, so the baseline score of 3 is appropriate.

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 retrieves the full contents of one document, using a specific verb ('get' implied, 'Read' in title) and resource ('document'). It distinguishes itself from sibling list_documents by explicitly focusing on a single document, which makes its 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 conveys that this tool is for retrieving a single document's full contents, which implies it is the appropriate choice when a specific document is needed rather than a list. It does not explicitly mention alternatives or exclusions, but the clear singular scope provides sufficient context for typical use.

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