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

The annotation readOnlyHint=false already indicates mutation, but the description goes further by stating that removal is permanent. This is a meaningful behavioral disclosure beyond what annotations convey. No other traits (e.g., auth, side effects) are mentioned, but the permanence is a key addition.

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 two concise sentences with no filler. The primary verb and resource are front-loaded, and the permanence note adds value without unnecessary length.

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 single-parameter delete operation, the description covers the essential behavior: the action, the target, and the permanence. There is no output schema, but none is needed for a void operation. The description is adequate for an agent to invoke it correctly, though it could optionally mention prerequisites or cascading effects.

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 input schema already fully describes product_id with 100% coverage. The description adds no additional meaning about the parameter, so it relies entirely on the schema. This matches the baseline of 3 for high schema coverage.

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 states the action (delete) and the target resource (product from Meta catalog), and distinguishes it from sibling create/update/list operations by naming the removal action. The added detail of permanence further clarifies the effect.

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?

The description implies usage for deleting a product, but it does not explicitly mention when not to use it or suggest alternatives (e.g., update_catalog_product for modifications). The purpose is unambiguous, but no context or exclusions are provided, so it relies on the agent's inference.

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