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 does disclose a behavioral trait: it returns the latest version, not a specific historical version. But it does not mention return format, not-found behavior, or any read-only guarantees. Since 'get' implies a fetch, this is a minimal but acceptable disclosure.

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?

A single sentence that is front-loaded and contains no filler. Every word contributes to meaning: 'Get', 'latest version', 'project document', 'by slug'.

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?

The tool is simple with two well-documented parameters, so the description is mostly complete. However, there is no output schema and the description does not explain the return shape or behavior for missing documents. Sibling context shows document-related tools exist, but the description doesn't clarify how this differs from get_master_document.

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%; both slug and projectId have useful descriptions in the schema. The tool description adds no extra parameter semantics, so the baseline 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 uses a specific verb and resource: 'Get the latest version of a project document by slug.' It clearly identifies the target resource (project document), the action (get), and the key parameter (slug). It also distinguishes from siblings like list_documents and get_master_document through 'latest version' and 'by slug.'

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?

Usage context is implied via 'by slug' and 'latest version' — the tool is for targeted retrieval of a specific document version. However, there is no explicit guidance on when to choose this over related siblings such as list_documents or get_master_document, and no alternatives are named.

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