Get issued document

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

With readOnlyHint=true already provided, the description adds value by disclosing the response content (entity, line items, payments, amounts) which is especially useful since there is no output schema. It does not contradict annotations and gives insight into what the agent will receive.

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, front-loaded sentence that clearly states the verb, target, and key details. There is no fluff or repetition; every word earns its place.

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 getter with full schema coverage and read-only annotation, the description is complete. It mentions the core purpose and return content. Missing explicit references to optional parameters (fieldset, company_id) but these are well-covered in the schema, so no significant gap remains.

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%, so the baseline is 3. The description's mention of 'by ID' adds no new meaning beyond the schema's document_id description. It does not elaborate on fieldset or company_id, but these are already fully documented in the schema.

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 single issued document by ID' with a specific verb and resource, and it enumerates the returned details (entity, line items, payments, amounts). This distinguishes it from siblings like list_issued_documents (collection) and get_received_document (received vs. issued).

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 for fetching one specific document by ID, which is clear given sibling names and the word 'single'. However, it does not explicitly mention alternatives such as list_issued_documents for multiple documents or when not to use this tool, but the context is strong enough.

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