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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description earns credit only for the sort order ('newest first') and the returned field set. It says nothing about pagination behavior or how the cursor/limit interact, which is the one behavioral detail an agent would still need.

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?

A single short sentence with no waste, and the key ordering information is front-loaded. Its terseness is close to under-specification (no verb, fragment structure), which keeps it below a 5.

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, listing the returned fields is a genuine contribution, and annotations cover safety. But for a 6-parameter paginated list tool with only 50% schema description coverage, the absence of any pagination or filtering guidance leaves real gaps.

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 only 50%: limit, status and include_archived carry no schema descriptions, and the description does not fill that gap — it never mentions filtering by status, archiving, or page size. The phrase 'with status, project, customer and total' refers to returned fields and can be confused with the project_id and status filters rather than clarifying them.

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 description names the resource (estimates) and states the ordering ('newest first') plus the fields returned, which implicitly distinguishes it from the singular get_estimate. However, it is a noun-phrase fragment with no verb, so the listing action is only inferred from the title rather than stated in the description itself.

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 guidance on when to use this tool versus get_estimate, list_projects, or the many other list_* siblings, and no mention of prerequisites or conditions. The only usable context (that it returns multiple estimates) is implicit.

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