delete_a_deal

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

The description adds the confirmation requirement beyond the annotations (destructiveHint=true). It reinforces the destructive behavior, but could mention idempotency or permanence.

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 repetitive, stating 'Delete a deal' three times and including unnecessary duplication. A more concise version would improve clarity.

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 delete tool with one parameter and no output schema, the description covers the core action and user confirmation. However, it omits details about soft/hard delete or response expectations.

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?

Parameter schema has 100% coverage, so baseline is 3. The description does not add any extra detail about the 'id' parameter beyond what the schema already provides.

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 clearly specifies that the tool deletes a deal, using a specific verb and resource. The emoji and 'DESTRUCTIVE' label further distinguish it from create, update, and retrieve siblings.

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?

Includes an explicit instruction to 'Confirm with the user before calling,' which provides a clear when-to-use guideline. However, it does not compare to alternatives or specify when not to use.

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