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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds value beyond that by naming what is actually destroyed (the estimate and its PDF) and that the action is irreversible, which the annotations do not specify. It does not mention permission requirements or any failure modes for already-deleted or in-use 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?

Three short sentences with the destructive nature front-loaded, followed by the ID requirement and the safety precondition. No filler or redundancy.

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 single-required-parameter destructive tool with rich annotations and no output schema, the description covers impact, irreversibility, and the confirmation step. The only gap is the optional display parameters, which the schema already documents adequately.

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 coverage is 100%, so the baseline is 3; the schema already explains all three parameters, including that customerName and estimateNumber are display-only. The description adds the provenance of the id ('from list_estimates') but says nothing about the optional confirmation-display fields, so it adds only marginal meaning.

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 and resource ('Permanently delete an estimate') plus the non-obvious side effect that the associated PDF goes too. An agent can distinguish this from list_estimates, fetch_estimate, or update_estimate without inspecting the schema.

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?

Gives an explicit route for obtaining the required argument ('use list_estimates to find it') and a precondition ('confirm with the user first'). It does not state when a user should choose this over, say, updating or voiding an estimate, but the destructive precondition covers the main decision point.

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