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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that — no error/not-found behavior, no cross-tenant scoping, no return-shape hint.

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?

One short sentence with zero padding and the resource front-loaded. Efficient, though its terseness borders on under-specification rather than optimized brevity.

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?

A simple single-id read with full annotation coverage and full schema coverage needs little, but with no output schema the agent gains no sense of what fields an adjustment returns or what happens on a bad id. Adequate, not complete.

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 parameter with 100% schema description coverage ("The invoice_adjustment id."). The description's "by id" restates the schema and adds no format, source, or example guidance, so baseline 3 applies.

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 resource (invoice_adjustment) with the singular-by-id scope. The phrase "one ... by id" implicitly separates it from invoice_adjustment_list, but no sibling is named.

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?

"by id" implies the precondition that a known identifier is required, and "one" implies the list tool for bulk retrieval. No explicit when-to-use or when-not-to-use statement, and no mention of invoice_adjustment_list as the alternative.

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