list_estimates

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List estimates' reveals nothing about permissions, rate limits, pagination behavior (despite pagination parameters in the schema), response format, or whether this is a read-only operation. The description fails to compensate for the lack of 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 maximally concise—a single two-word phrase. While this leads to under-specification in other dimensions, it contains zero wasted words and is front-loaded with the core action. Every word earns its place, even if more content is needed.

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?

Given the tool's complexity (a list operation with pagination), lack of annotations, 0% schema coverage, and presence of an output schema, the description is inadequate. It doesn't explain what 'estimates' are, how results are structured, or behavioral constraints. The output schema existence means return values might be documented elsewhere, but the description should still provide context for invocation.

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%, meaning parameter titles ('Page', 'Per Page') are generic and unhelpful. The description adds no parameter information whatsoever—it doesn't mention pagination, default values, or how parameters affect results. With two undocumented parameters, the description fails to compensate for the schema's deficiencies.

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 'List estimates' is a tautology that restates the tool name without adding specificity. It doesn't distinguish this tool from sibling list tools like 'list_clients' or 'list_invoices' beyond the resource type. While it identifies the verb ('List') and resource ('estimates'), it lacks any detail about scope, filtering, or what constitutes an 'estimate' in this context.

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. It doesn't mention sibling tools like 'get_report' that might provide similar or overlapping functionality, nor does it specify prerequisites, context, or exclusions. Users must infer usage from the tool name alone.

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