Delete Review Bundle

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

Goes well beyond the destructiveHint=true/non-idempotent annotations by scoping the damage: the bundle and its shared review link are removed, the contained media are NOT deleted, and the action is irreversible. That scope information is exactly what an agent needs before committing a destructive call.

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 core sentence is well front-loaded and the destruction-scope note earns its place, but the trailing permission block and boilerplate about sharing access, notifying people, or provider charges read like template noise of questionable relevance to a delete.

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?

Covers destruction scope, irreversibility, permission requirements, and the confirm guard, and no output schema is needed for a delete. It stops short of describing failure behavior (e.g., unknown id) or whether the shared link revocation is immediate, which would close the remaining gap.

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%, so account, confirm, and review_bundle_hashed_id are already documented in the schema with equal or greater detail. The description's mention of 'hashed id' and confirm adds no syntax beyond the structured fields, so 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?

States a specific verb and resource ('Permanently deletes a review bundle') plus the identifier used to select it. It is clearly distinguishable from siblings like create_review_bundle and list_review_bundles.

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?

Provides prerequisites (required permission, confirm=true, delegation caveat) rather than when-to-use guidance. There is no comparison to alternatives or statement of when deletion is appropriate, so usage is only implied.

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