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

Annotations already carry the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds genuinely useful context beyond that: results are ordered newest first, pages hold up to 50 estimates, and it requires a Cotlet API key with access to this app. It stops short of describing cursor semantics or rate limits.

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?

Front-loaded with the core behavior, which is good, but the status example "Customer Approved or Customer Declined" appears twice verbatim, and the options/totals theme is restated across two sentences. Roughly a sentence's worth of redundancy for a short description.

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 does the work of describing the return payload (options, per-option totals, Housecall Pro status), ordering, page size, and the auth prerequisite. That is close to what an agent needs; it only lacks guidance on cursor progression details.

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 100%, so the schema already documents limit, cursor, status and customer_id, including the 1-50 range and default of 20. The description's mention of "pages hold up to 50" and filtering by customer/status echoes the schema rather than adding syntax or format detail. Baseline 3 is appropriate.

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 estimates) and specifies the payload each item carries: options, totals, and status. It also gives ordering (newest first), which an agent needs to interpret results. It does not explicitly differentiate itself from sibling estimators like service-fusion_list_estimates or workiz_list_estimates, but the Housecall Pro prefix and estimate-specific detail make intent unambiguous.

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?

"Filter by customer or by status to find estimates that still wait for an answer" implies a usage scenario (finding pending approvals), which nudges the agent toward the status/customer_id params. However, it names no alternatives or when-not conditions, and there are many sibling list_estimates tools across providers with no routing guidance.

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