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

readOnlyHint=true already covers the safety profile. The description contributes genuinely useful context — that each result carries its customer, address, schedule and options, and the underlying GET /estimates endpoint — but says nothing about pagination behavior or default ordering. With annotations carrying the safety burden, a 3 is fair.

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 compact sentences with the resource and its filter dimensions front-loaded, plus a one-line endpoint reference. Efficient, though the endpoint citation is marginal value for an agent that only needs to call the tool.

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?

For a 12-parameter, all-optional list tool with no output schema, the description covers the filter surface and hints at the shape of a returned record. It stops short of describing pagination defaults or the full return structure, but nothing required to invoke it correctly is missing.

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 all 12 parameters are already documented in the schema with enums and ISO-8601 format notes. The description restates a subset of the filters (customer, work status, employees, scheduled window) without adding syntax or semantics beyond the schema, so baseline 3 applies.

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+resource ("List estimates") and enumerates the filter dimensions, so the agent knows this is a filtered collection read. It contrasts implicitly with the singular get_estimate sibling via plural 'list', but does not name it explicitly.

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?

The filterable dimensions (scheduled window, customer, employees, work status) imply when the tool is useful, but there is no explicit when-to-use vs when-not guidance and no named alternative to fall back on. Usage is left to inference.

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