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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Read-only; changes nothing' largely restates structured data. What the description does add is the hard cap of 10 results (a truncation behavior the schema doesn't reveal) and the shape of each result, which is genuinely useful.

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 short sentences, front-loaded with the resource and scope, with no filler. Every clause ('10 most recent', the field list, read-only) carries information.

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?

With no parameters and no output schema, the description carries the burden of explaining return values and does so by enumerating title, client, status, total and link. Minor gaps remain: it doesn't say what orders 'most recent' (created vs. modified) or what happens when fewer than 10 quotes exist.

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?

The tool takes zero parameters, so there are no parameter semantics to explain and the baseline is 4. The description correctly spends no words on parameters and instead documents the output fields.

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 ('Show the contractor's ... FieldDraft quotes') plus an explicit scope ('10 most recent') and the fields returned, so the agent knows exactly what comes back. It does not name or contrast with the sibling `list_quotes`, which is the obvious alternative and is left for the agent to infer.

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?

Usage is only implied: the fixed '10 most recent' framing suggests a quick glance rather than a paginated enumeration, but there is no explicit when-to-use or when-not clause, and `list_quotes` is never mentioned as the alternative. The 'Read-only; changes nothing' line signals safety, not selection guidance.

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