hcp_list_estimates

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context beyond annotations: automatic pagination behavior and the cents-to-dollars price conversion. No contradiction with 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 two short sentences with no fluff. The core listing intent is front-loaded, followed by the two most important behavioral notes: auto-pagination and price unit conversion.

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 output schema and annotations cover return values and safety, so the description does not need to explain those. However, with six optional parameters and zero schema descriptions, the description is only minimally complete for helping an agent pass correct filters and date strings. It gives enough to attempt a call but not enough to be confident about parameter semantics.

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, but it only says 'optional filters' without describing any specific parameter, format, or valid values. The parameter names like customer_id and scheduled_start_min are somewhat self-explanatory, but details like date format, work_status accepted values, or pagination semantics are left undocumented.

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 a clear verb and resource: 'List estimates with optional filters.' It distinguishes this from the sibling hcp_get_estimate by implying a multi-record listing operation. However, it does not explicitly contrast itself with other list_* siblings or state what kind of estimates are included.

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 notes that filtering and pagination are optional ('optional filters', 'auto-paginates unless explicit page is set'), which gives useful operational context. It does not explicitly say when to prefer this tool over hcp_get_estimate or other list tools, nor does it mention any exclusions.

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