get_invoice

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

With no annotations, the description carries the full burden. It discloses that the tool returns the 'complete record', which conveys the nature of the response. It does not address error handling, permissions, or rate limits, but for a simple read operation this is acceptable though not thorough.

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 with no unnecessary words. It precisely states the action, the resource type, and the identifier used, earning full marks for conciseness.

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 retrieval tool, the description covers the purpose and the parameter semantics adequately. It notes the result is a 'complete record' and identifies the ID type. It does not describe output schema or error conditions, but the simplicity of the operation and existing sibling context make this sufficient.

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 input schema provides only a generic property name 'Invoice Id' with zero description coverage. The description compensates by clarifying that 'invoice_id' is the 'Elorus ID', giving essential semantic meaning and making the parameter unambiguous.

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' and identifies the exact resource: 'complete record of a single sales invoice'. It also specifies the identifier used ('Elorus ID'), clearly distinguishing this single-record retrieval tool from the sibling 'list_invoices' tool.

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 when you already have an Elorus ID for an invoice and need the full record. However, it does not explicitly state when to use this tool instead of list_invoices, nor does it mention any exclusions or alternatives.

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