get_document

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

No annotations are provided, so the description must disclose behavior fully. It clarifies that 'cluster' is optional with a default, but fails to mention authorization, rate limits, or error behavior (e.g., if document not found). As a read operation, no side effects are stated.

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 concise: one clear purpose sentence followed by a focused parameter list. No extraneous words, and the structure front-loads the main action.

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 output schema exists (so return values are documented), the description adequately covers parameter roles. However, it lacks details on error conditions, required permissions, or behavior in edge cases (e.g., non-existent document). For a simple retrieval tool, this is adequate but not comprehensive.

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 0%, so the description must explain all parameters. It does so clearly: 'index', 'id', and 'cluster' with optionality and default. While brief, it adds value beyond the schema by specifying that cluster uses the default if omitted.

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 'Get a document by ID', providing a specific verb and resource. It is easily distinguished from siblings like 'delete_document' and 'index_document', and the retrieval by ID contrasts with 'search_documents'.

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 document ID, but does not explicitly state when to use this tool over alternatives (e.g., search_documents). No when-not or prerequisites are provided.

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