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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and repeatability are fully covered. The description's only addition is that the payload includes line items and the remaining open amount, which is useful but thin. It says nothing about what 'open' means (unpaid vs. unapplied credit), so behavioral context beyond annotations is minimal.

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?

A single short sentence with the key noun front-loaded and no filler. Its brevity costs it though — the same word budget could have carried the retrieve verb and the return scope.

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?

No output schema exists, so the description carries the burden of describing returns, and it only sketches them ('lines and what is still open'). For a simple single-id read tool this is roughly adequate, but an agent cannot tell whether open balances are per-line or header-level, or whether related payments and credits are included.

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 a single required parameter at 100% schema description coverage, so the schema fully documents invoice_id. The description adds nothing about where to obtain a valid invoice id or what happens with an unknown id, which is the normal baseline-3 case when the schema already does the work.

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 names the resource (invoice) and hints at the return content (lines and open balance), and the tool name supplies the retrieve verb. However 'Invoice with lines and what is still open on it' is closer to a label than a stated action, so an agent must infer that this fetches a single invoice by id rather than listing invoices. It does not distinguish itself from siblings such as o2c_get_order, o2c_customer_statement, or solo_get_invoice.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The agent is left to infer from the name alone whether to call this versus o2c_get_customer, o2c_ar_aging, or o2c_get_order to answer an invoice question.

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