List Estimates

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

There are no annotations, so the description bears full responsibility for behavioral disclosure. It states the tool is paginated, but does not describe the return format, whether it is read-only, response structure, or any rate limits. This is minimal for a tool that lists potentially many estimates.

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 sentence, 'List/search estimates, paginated,' followed by a docs link. It is concise and front-loaded, with no redundant words. The docs link provides additional reference without cluttering the 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?

The tool has no output schema, yet the description does not explain what the response contains (e.g., estimate objects, fields, pagination metadata). The docs link is provided, but the description alone is insufficient for an agent to know what to expect. Given the complexity of the extra_query parameter shape, more context would be valuable.

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 five parameters have descriptions in the schema (100% coverage), so the description doesn't need to add parameter details. The description's mention of 'search' aligns with the extra_query escape hatch but adds no specific parameter semantics. Thus, the schema itself carries the parameter documentation.

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 states 'List/search estimates, paginated,' which clearly identifies the tool's action (list/search) and resource (estimates), distinguishing it from other list tools for different resources. It also mentions pagination, which is a key feature. This is specific and not a tautology.

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 provides no guidance on when to use this tool versus alternatives such as get_estimate for retrieving a single estimate. It does not mention any prerequisites, exclusions, or scenarios where this tool is preferred. The only usage hint is the verb 'search,' which implies filtering, but no explicit alternatives are given.

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