customer_review_responses_delete_instance

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

No annotations are provided, so the description carries full behavioral burden, yet it discloses nothing about irreversibility, required permissions, or what happens to the parent review once its response is deleted. 'DELETE' implies mutation, but for a destructive, annotation-free tool this is a significant transparency gap.

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 content is a single line, but it is literally duplicated – 'DELETE /v1/customerReviewResponses/{id} (DELETE /v1/customerReviewResponses/{id})' – which is pure waste rather than concision. Being short here reflects under-specification, not efficiency.

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 delete operation with no annotations and no output schema, the description should at minimum explain the effect and any safety context. It provides only a raw endpoint string, leaving an agent unable to reason about consequences.

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 single required parameter 'id' is fully documented in the schema (100% coverage) as 'the id of the requested resource'. The description adds nothing beyond the path template, but with complete schema coverage the baseline of 3 applies.

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 states the verb (DELETE) and the resource (customerReviewResponses) with an id path parameter, so the basic operation is identifiable. However, it merely restates the tool name and HTTP path verbatim, with the path duplicated in parentheses, adding no semantic explanation of what a 'customer review response' deletion means in this API.

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?

There is no guidance on when to use this tool versus siblings such as customer_review_responses_get_instance or customer_review_responses_create_instance. The agent must infer entirely from the name that this is the destructive counterpart. No prerequisites, no caveats, no alternates are mentioned.

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