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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not state whether deletion is permanent or reversible, whether it requires elevated permissions, or what happens to dependent data.

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?

A single grammatical, front-loaded sentence with no wasted words. It is concise but achieves that partly through under-specification rather than disciplined editing.

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 mutation with no annotations detail beyond hints, no output schema, and zero parameter documentation, the description is far too thin. An agent cannot confirm scope, permanence, or parameter roles before invoking an irreversible operation.

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?

Three required parameters (projectId, siteId, productId) with 0% schema description coverage, and the description supplies no meaning for any of them. The phrase 'from the catalog' hints at scope but does not map to projectId/siteId, so the description fails to compensate for the documentation gap.

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?

Clear verb+resource: 'Delete a product from the catalog' tells the agent exactly the operation and object. However, it does not distinguish itself from siblings such as set_product_status (likely a soft status change) or update_product, leaving ambiguity about hard vs. soft removal.

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 when-to-use guidance, no prerequisites, and no mention of alternatives like set_product_status for deactivation. The agent must infer from the name alone when this is the right tool versus its siblings.

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