Get Purchase Document

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

Annotations already cover the read-only/non-destructive safety profile. The description adds value by disclosing the response shape (JSON with full document fields, items, categories, tags, and duplicate info), which is not available from an output schema since none is present.

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?

Clear, front-loaded summary followed by argument details and return type. Minor redundancy between 'Returns full document details...' and the later 'Returns...' line, but overall compact and scannable.

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 read-only get-by-ID tool with one parameter and rich annotations, the description provides enough information to invoke it correctly. It does not explain error behavior or auth requirements, but those are not essential for this simple read operation.

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 only parameter is fully documented in the schema with type, format, and resource ID description; the description restates it as 'id (string): Document ID (UUID format)' without adding much new meaning. Schema coverage is high, so baseline 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?

States a specific verb ('Get'), resource ('details of a single purchase document'), and access pattern (by ID). It also enumerates the returned content, making it easy to distinguish from list or image siblings.

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 clearly implies this tool is for retrieving one purchase document by ID, but it does not explicitly contrast with sibling tools like ogarniai_list_categories or ogarniai_get_document_image. Context is present, but no explicit when-to-use or when-not-to-use guidance is given.

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