gbp_delete_review_reply

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

With no annotations, the description carries full responsibility for behavioral disclosure, yet it only restates the mutation. It does not warn that deletion is permanent, explain that the review itself remains intact, or note any required permissions. For a destructive tool this is a significant 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?

A single six-word sentence, front-loaded with the verb and object, with no fluff. Every word earns its place and the structure is immediately scannable.

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?

The tool has only one parameter and no output schema, so the description is close to sufficient. However, it lacks usage prerequisites and any behavioral warning for an irreversible action, leaving an agent to infer important context from sibling names.

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 description coverage is 100% and the parameter already specifies 'Full review resource name'. The tool description adds no additional meaning about how to obtain that name or whether it refers to the review or the reply resource, so it is neither harmful nor additive.

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 names a specific verb ('Deletes') and a specific resource ('a reply to a review'), which clearly distinguishes it from sibling tools like gbp_reply_review for creating/updating a reply and gbp_list_reviews for reading reviews. An agent can understand the exact operation from this line alone.

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 about when to use this tool instead of gbp_reply_review or whether it should be used after listing reviews. The sibling list implies the context, but the description does not state any usage conditions, prerequisites, or exclusions.

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