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

Adds significant context beyond annotations: permanence, and that document lines retain copies of name/price. This reassures about side effects. 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?

Three sentences, each adding distinct value: the action, the dependency behavior, and the absence of a bulk option. Information is front-loaded with the primary purpose.

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 one-parameter destructive tool, the description covers all necessary details: permanence, effect on dependent data, and no bulk alternative. No output schema exists, so no return info is needed.

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 only parameter, id, is referenced as 'by id' in the description, which clarifies its role. Schema coverage is 0%, but the description adequately compensates for a single simple parameter.

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?

Clearly states the action (permanently delete) and the resource (product by id). The mention of no bulk variant distinguishes it from sibling bulk-delete tools.

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?

Explicitly states when to use this tool: to delete a single product by id, and notes the absence of a bulk variant, preventing search for a non-existent sibling.

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