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 of disclosing behavior. It states that metadata and OCR text are retrieved, implying a read operation, but it does not disclose the effect of include_content, failure behavior, response shape, or whether this is a safe side-effect-free operation.

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 focused sentence with no filler. It is concise and readable, though slightly under-specified given the include_content parameter.

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?

With no annotations and no output schema, the description leaves meaningful gaps: the semantics of include_content, what the returned metadata contains, and any error conditions. It is minimally viable for a simple get-by-ID tool but not fully complete.

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 0%, so the description must compensate for parameter meaning. 'By ID' hints at document_id's role, but include_content is not explained at all; the description does not clarify that include_content likely controls whether the OCR text is returned, nor does it describe expected formats.

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 ('Retrieve') and names the resource ('document metadata and extracted OCR text') and the key selector ('by ID'). This clearly states what the tool does, though it does not explicitly distinguish it from sibling like download_document.

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 phrase 'by ID' implies this tool is for fetching a specific document rather than searching or listing, so usage context is inferable. However, it does not explicitly mention when to use this tool instead of alternatives such as search_documents or download_document.

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