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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value with the ordering rule ("newest first") and the implication that omitting filters returns everything, but says nothing about pagination behavior beyond the limit cap or response shape.

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 tight sentences with zero filler. The core behavior and ordering are front-loaded, and the filter enumeration follows immediately.

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?

This is a simple read-only list tool with rich annotations and a fully documented schema, so little is needed. However, with no output schema, the description should say something about what a result entry contains, and it leaves the discrepancy in allowed status values unresolved.

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 coverage is 100%, so baseline would be 3, but the description's status list ("draft, sent, accepted, rejected, paid, overdue") conflicts with the schema's enum values ("draft, sent, viewed, accepted, rejected, invoiced"). An agent trusting the description could send "paid" or "overdue" and get a rejected call, so the description actively misleads rather than adding meaning.

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 states a specific verb and resource ("Lists quotes or invoices") plus an ordering guarantee ("newest first"). It does not differentiate from overlapping siblings such as fetchQuoteDrafts or fetchQuoteHistory, which an agent would need to choose between.

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?

It lists optional filters but gives no explicit when-to-use or when-not-to-use guidance, and no pointer to the sibling tools that fetch drafts or history. The agent is left to infer that this is the general-purpose listing endpoint.

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