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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds 'Paginated' and the REST GET method, which reinforces read-only behavior, but does not disclose return formats, rate limits, or other execution details. This is adequate but not rich beyond 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 description is three short clauses, front-loaded with the verb and resource, then filters, pagination, and endpoint. Every phrase adds value and there is no redundancy or filler.

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 read-only list tool with full schema coverage, the description captures the core operation, optional filters, pagination, and endpoint. However, with no output schema, it omits the response structure and default pagination limits, which are minor gaps for such a tool.

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?

All 7 parameters are fully described in the input schema (100% coverage), so baseline 3 applies. The description groups them as 'client, state, date range, or updated-since' and mentions pagination, which loosely maps to page/per_page, adding slight semantic organization. No additional syntax or behavioral detail beyond the schema.

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 opens with 'List estimates'—a specific verb and resource—and enumerates optional filters (client, state, date range, updated-since) plus pagination. This clearly distinguishes it from sibling list tools (e.g., list_invoices) by naming the resource and its filter dimensions. The REST endpoint reinforces the scope.

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 description implies usage context: use when you need to list estimates with optional filters. It does not explicitly name alternatives or exclusion criteria, but the resource name and sibling context make the appropriate use clear. Lacks an explicit 'when not to use' statement.

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