hcp_get_estimate

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

Annotations already establish this is read-only, idempotent, and non-destructive. The description adds a meaningful behavior beyond those annotations: prices are converted from cents to dollars, which an agent would not otherwise know.

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?

One sentence, two clauses, no filler. The purpose and the key output behavior are both delivered without wasted words.

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 single-parameter read tool with an output schema and safety annotations, the description covers everything needed to invoke it correctly. No pagination, mutation, or complex precedence concerns apply.

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?

The schema only defines estimate_id as a string with no further documentation. The description compensates by explaining the expected format ('csr_ prefix'), which gives the agent concrete guidance beyond the raw schema.

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 ('Get'), a specific resource ('a single estimate'), and the lookup key ('by ID'), with the useful csr_ prefix detail. This distinguishes it from list-style siblings like hcp_list_estimates.

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 phrase 'single estimate by ID' clearly implies this tool is for point lookups when an estimate ID is already known, rather than for enumerating estimates. It does not explicitly name hcp_list_estimates as the alternative, so it stops short of full exclusion guidance.

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