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. It only restates the read operation ('Get') and does not disclose potential errors, authentication requirements, response structure, or behavior when the UUID is invalid. This is minimal transparency beyond the purpose itself.

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 followed by a useful documentation link. There is no fluff or redundant detail, and 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 one-parameter read tool with no output schema and no annotations, the description is adequate: it identifies the resource and the lookup key, and the docs link supplements missing details. The return value is predictable from the name and verb, so it does not need extensive explanation.

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 has 100% coverage for its single parameter, which is described as 'Invoice UUID.' The description adds no extra meaning beyond saying 'by its UUID', so the schema already carries the semantic weight. 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?

The description uses the specific verb 'Get' with the resource 'single invoice' and the identifier type 'UUID', making it clear this tool fetches one invoice as opposed to listing invoices. It clearly distinguishes from sibling tools like list_invoices and list_job_invoices.

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 states it retrieves a single invoice by UUID, which clearly implies use when you already have the invoice UUID. It does not explicitly mention alternatives or exclusions, but the context is clear enough for a simple getter.

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