products_delete_product_review

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

The description adds no behavioral information beyond what annotations already provide (destructiveHint=true, idempotentHint=true). It does not mention side effects, irreversibility, or permissions, and without such context the agent cannot anticipate the consequences of deletion beyond the raw annotation flags.

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 extremely short (three words) and concise, but it essentially restates the tool name. It lacks structure and does not 'earn its place' by adding meaningful detail beyond the name. It is not verbose, but it is under-specified.

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 tool with no output schema, the description should provide at least some contextual information about the operation (e.g., irreversibility, scope, or prerequisites). It offers none, leaving the agent to infer behavior from annotations alone. This is insufficient for a deletion action.

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?

Schema coverage is 100% – all parameters have descriptions in the schema. The description provides no additional parameter semantics, so it does not improve upon the structured documentation. Baseline of 3 is appropriate when the schema covers all parameters and the description adds nothing extra.

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 'Delete Product Review' clearly states a specific action (Delete) and resource (Product Review), which is distinct from sibling tools like products_delete_product_by_id or products_delete_product_collection. It does not add extra context but is unambiguous and not misleading.

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 provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description does not differentiate it from other delete tools or mention conditions under which it should be used.

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