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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the default result set (awaiting_acceptance) and the auth prerequisite (a Cotlet API key with access to this app), which are behavioral facts not present in the 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?

The first sentence duplicates the second almost verbatim ('Quotes with customer, total, quote date, expiry date and status' vs 'Lists quotes with customer, total, quote date, expiry date and status'), wasting space. The remaining guidance is front-loaded and efficient, but the redundant opening should be cut.

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 output schema, the description compensates by listing the returned fields and stating the default filter and auth requirement, which is enough for an agent to call it correctly. Pagination/ordering is left to the limit parameter in the schema, a minor gap.

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 the baseline is 3, but the description goes beyond the schema by explaining the cross-parameter behavior of status+since and the default status filter, which the schema only documents in isolation. This adds genuine filtering semantics.

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 clear verb+resource ('Lists quotes') and enumerates the fields returned (customer, total, quote date, expiry date, status), which differentiates it from sibling write tools like tradify_create_quote and tradify_send_quote. The opening fragment 'Tradify: Quotes with customer, total...' is a redundant restatement of the following sentence rather than additional information, keeping it out of the top tier.

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?

Gives explicit usage context: default retrieval returns quotes awaiting acceptance, and to find quotes accepted in a period use status=accepted with a since date. This is a concrete when-to-use pattern. It does not name any alternative tool, so it falls short of a full 5, but the scenario guidance is real.

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