hcp_list_estimate_line_items

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

Annotations already disclose the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false). The description adds one genuinely useful behavioral detail beyond the annotations: 'Prices converted from cents to dollars,' which tells the agent the returned data is transformed. 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?

Two short sentences with the action front-loaded and the conversion behavior delivered in a single clause. Every word earns its place; there is no filler or repetition of schema content.

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 tool with two required string params, an output schema covering return values, and annotations covering the read-only/idempotent profile, the description is mostly complete. It adds the important cents-to-dollars transformation, but lacks explicit routing guidance and does not clarify the estimate-option ID hierarchy. These are modest gaps for a tool this simple.

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 carries the burden for explaining estimate_id and option_id, but it does not compensate. It never explains what the two IDs mean, how they relate (e.g., which option belongs to which estimate), or where to obtain them. The parameter names are mildly self-explanatory, but no relationship or format guidance is provided.

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?

States a specific verb (list), resource (line items), and scope (for a specific estimate option). The 'estimate option' scoping distinguishes it from the closest sibling hcp_list_job_line_items as well as estimate-level siblings hcp_list_estimates and hcp_get_estimate.

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 scope phrase implies when to use it — when you need line items for a particular estimate option — but there is no explicit when-to-use guidance, no exclusion criteria, and no mention of alternatives such as hcp_list_job_line_items or hcp_get_estimate. Usage is implied, not stated.

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