get_estimates

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

The readOnlyHint annotation already declares this is a safe read operation, and the description's 'List' wording matches that. It adds useful context about optional pagination and filters, but does not disclose defaults, result ordering, pagination limits, or response shape.

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 a single front-loaded sentence with no fluff. Every element—resource, operation, and optional modifiers—earns its place.

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 simple read-only list tool with four optional parameters, the description is adequate but not fully complete. It does not describe the return format, pagination defaults, or how the filters behave, and there is no output schema to fill that 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 description coverage is 0%, so the description must compensate for the four undocumented parameters. It groups page/limit as 'pagination', search as 'search', and customer_id as 'customer filters', adding high-level meaning beyond raw types, but it omits details like page numbering, limit constraints, and search scope.

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 uses the specific verb 'List' with the resource 'estimates', making the operation unambiguous. The plural resource and optional pagination/filter phrasing clearly differentiate it from singular siblings like get_estimate and from other resources like get_invoices.

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 this tool is for fetching a list of estimates with optional filters, but it never explicitly says when to prefer it over get_estimate or get_customer_invoices. Usage context is implied by 'List' and the filter parameters, not stated directly.

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