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 the safety profile is covered. The description adds scope information by naming two allocation views (whole-document and printed-line), but with no output schema present it does not describe the return shape, pagination, or what happens when no allocations exist.

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 front-loaded sentence with no filler. It is efficient, though so terse that the domain terms are left unglossed.

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 read-only single-parameter tool with no output schema, the description covers what is fetched but not the returned structure or edge cases. Given there is no output schema to fall back on, a short note on what the allocations contain would materially help.

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?

Schema description coverage is 0% and the single parameter is a nested InvoiceId object with an undescriptioned uuid field. The description's phrase 'this invoice's' implies the invoice scoping, and the parameter name is largely self-explanatory, but the description adds no explicit statement that it takes an invoice UUID.

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?

States a specific verb ('Read') and a specific resource (an invoice's whole-document and printed-line load allocations), which distinguishes it from siblings like get_load_costs or list_loads. The term 'load allocations' is domain jargon and the distinction between 'whole-document' and 'printed-line' is not explained, so an agent knows what it reads but not exactly what those two categories mean.

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 guidance on when to use this tool versus get_invoice, get_invoice_line_items, get_load_costs, or assign_invoice_load. The description implies read-only retrieval of existing allocations but never states prerequisites (e.g. invoice must be initialized/reviewed) or exclusions.

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