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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds nothing behavioral beyond that: it omits that results are paginated and, critically, that the default status filter is 'awaiting_acceptance' — a caller expecting all quotes would be silently misled.

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?

It is short and front-loaded with zero filler, but it is a sentence fragment rather than a definition, so brevity comes at the cost of meaning. The space used is not wasted, yet it does not earn its place by conveying an operation.

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 five filter/pagination parameters, a non-obvious default status, and no output schema, the description should carry real weight. Enumerating return fields gives partial credit for the missing output schema, but pagination, defaults, and filter behavior go unexplained, leaving the agent under-informed for a tool it will likely call often.

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 80%, so the schema already documents since, cursor, search, and status; the baseline of 3 applies. The description's mention of 'status' and 'quote date' loosely aligns with the status/since filters but adds no syntax, default, or interaction detail, and says nothing about the undocumented limit parameter.

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 text is a noun fragment ('Quotes with customer, total, quote date, expiry date and status.') that largely restates the title 'List quotes' while enumerating return fields. It never states a verb or scope (e.g., 'Lists quotes'), so an agent must infer the operation from the name rather than the description, and nothing separates it from siblings such as create_quote, send_quote, or list_invoices.

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 when-to-use guidance, no mention of the other list tools (list_invoices, list_jobs, list_customers), and no note about prerequisites or exclusions. The agent gets no signal about choosing this tool over any sibling.

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