get_invoice

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

No annotations are provided, so the description carries the full burden. 'Get full details' is a weak behavioral signal: it does not state what fields are returned, whether the call is read-only, what happens for an unknown invoice ID, or whether any special permissions are needed.

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?

One short, front-loaded sentence with no filler. 'Full details' and 'specific' earn their place, and the description is appropriately sized for a single-parameter retrieval tool.

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 get-by-id tool, this is close to adequate, but with no output schema and no annotations, 'full details' remains undefined. The agent cannot know exactly what invoice data will be returned or how errors are surfaced, and it is not guided to list_invoices when the ID is unknown.

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?

There is one required parameter, invoiceId, with 0% schema description coverage. The description's 'a specific invoice' implies that invoiceId identifies which invoice to retrieve, but it does not explain the ID format, provide an example, or clarify where to obtain the ID.

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 the verb 'Get' with the resource 'invoice' and adds 'specific', so it clearly targets a single invoice rather than a list. This distinguishes it from siblings like list_invoices, export_invoice_json, and generate_invoice_pdf without needing to open the schema.

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?

Usage is implied: use this when you need full details for one known invoice. However, the description never contrasts with list_invoices for enumeration or export_invoice_json/generate_invoice_pdf for output formats, and it provides no explicit 'when not to use' guidance.

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