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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds two genuinely useful facts: results are paginated/bounded, and financial values are permission-gated and will be redacted without it. That permission caveat is exactly the kind of behavior not expressed in annotations.

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?

Two sentences, zero waste, with the core action and scope front-loaded before the permission caveat. Nothing is repeated from the title or schema.

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 and the schema is undocumented, so the description should say more about what an entry in the page contains (invoice identifiers, allocation amounts). It conveys read-only pagination and permission gating, but the return shape and an error case (unknown trip_number) remain unexplained.

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%, so the description must carry the burden. It partially does: 'one exact load' signals trip_number must be an exact identifier, and 'bounded page' signals limit/offset paging, but it states no default (25), cap (100), or offset bound that the schema leaves undocumented.

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 and resource: reading a bounded page of contributing invoices for one exact load. That is clearly distinguishable from broad siblings like search_invoices or list_loads, though it never names the inverse sibling get_invoice_loads or any other alternative to clarify the boundary.

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 use case is implied (fetch invoice cost contributions for a given trip) but there is no explicit when-to-use, when-not-to-use, or alternative routing. An agent must infer that get_invoice_loads is the inverse relation and that this tool is the load-centric path to the same data.

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