get_invoice

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

With no annotations provided, the description carries the full burden. It discloses what the tool returns (line items, payments, totals), but does not explicitly state that it is a read-only operation or describe behavior on missing IDs. While 'Get' implies read-only, more detail would improve transparency.

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, well-structured sentence that conveys the tool's purpose and key output components without any unnecessary words. It is front-loaded with the verb and resource.

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 simplicity of the tool (one parameter, no output schema), the description is mostly complete. It covers the purpose and what the returned data includes. It could additionally mention that it retrieves a single invoice, but this is strongly implied by the 'id' parameter and the use of 'an invoice'.

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 schema fully documents the only parameter (id as 'The invoice UUID'), so the description adds no additional parameter-level meaning. The description does mention the output types, which indirectly clarifies the parameter's purpose, but this is not parameter-specific detail.

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 ('Get detailed information') and identifies the resource ('an invoice') with a clear scope ('including line items, payments, and totals'). It distinguishes itself from sibling tools like list_invoices by focusing on a single invoice's details.

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 that this tool is for retrieving a single invoice's details, but it does not explicitly state when to use it versus alternatives (e.g., list_invoices) or mention any exclusions. The single 'id' parameter hints at targeted lookup, but no explicit guidance is provided.

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