Delete estimate

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

The description says 'Destructive,' but this only restates the existing destructiveHint=true annotation and adds no new behavioral context—no mention of permanence, cascading effects on related records, permissions, or constraints on deleting converted estimates. With annotations carrying the safety profile, the description contributes no incremental transparency.

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 very short and front-loaded with the action, containing no padding. One minor deduction because 'Destructive' is redundant with the destructiveHint annotation, so not every word adds incremental value.

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 destructive operation with no output schema, the description leaves important domain context unstated—such as whether an estimate can be deleted after being sent or converted to an invoice. The schema and annotations provide required parameters and safety flags, but the description alone does not give an agent enough caveats to avoid misuse.

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?

Only 50% of parameters have schema descriptions; estimateId has no description, and locationId is documented in the schema. The tool description mentions neither parameter, so it adds no meaning beyond the schema for identifying which estimate to delete or how the default location behaves.

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 uses a specific verb and resource, 'Delete an estimate,' which unambiguously identifies the operation and distinguishes it from the many delete-* siblings by naming the resource. The appended 'Destructive' reinforces the nature of the action.

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?

No guidance is given on when to choose this tool over alternatives such as ghl_update_estimate, ghl_send_estimate, or ghl_estimate_to_invoice. The description merely states the action, leaving the agent to infer usage from the tool name.

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