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 of behavioral disclosure. It only states a simple read operation but omits any details about authorization, rate limits, idempotency, or potential side effects. The tool appears to be a safe read, but the description is too minimal to confirm.

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 very concise (one sentence), but it may be too brief given the lack of supporting detail. It front-loads the core purpose but sacrifices completeness for brevity.

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?

The tool has an output schema, so return values are likely documented elsewhere. The operation is simple (get by ID). However, the description does not mention error handling, null results, or any additional context that would help an agent handle edge cases. It meets the minimum viable standard but has clear gaps.

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 description adds no meaning beyond the schema. Schema description coverage is 0%, meaning the property 'invoice_id' has no documentation in the schema. The description fails to provide any context or constraints for the parameter (e.g., format, example, source).

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 'Get an invoice by ID' clearly specifies the action (get), resource (invoice), and method (by ID). It effectively distinguishes from sibling tools like 'list_invoices' and 'get_invoice_download_url'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., list_invoices or get_invoice_download_url). There is no mention of prerequisites, context, or exclusions.

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