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

Annotations only flag destructiveHint/readOnlyHint/idempotentHint; the description goes further by naming the exact cascading data loss (mentions, search results, shopping results), declaring the operation irreversible, and describing the human-confirmation gating. That is material context an annotation cannot express.

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?

Three tight sentences: effect and blast radius first, irreversibility second, required workflow third. No filler, and the most decision-critical information is front-loaded.

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?

An output schema exists, so return values need no explanation, and the safety/confirmation story is complete. The only gap is that the requestId parameter and the identifier parameters remain undocumented, which an agent may need to disambiguate.

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 0% across 5 parameters, so the description must compensate. It explains confirmationToken in depth (how to obtain and when to send it), but organizationId, projectId, competitorId and requestId carry no meaning in either place, so the compensation is only partial.

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 precise verb (remove) and resource (competitor from a project) and enumerates the cascade scope: every mention, search result and shopping result. This clearly separates it from sibling deletions such as delete_cluster, delete_tracked_queries and archive_project.

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?

Gives an explicit precondition and workflow: a confirmationToken is required, obtain it by calling preview_operation with tool "delete_competitor" and the same arguments, show the plan to the user, and only call this tool after explicit user agreement. When-to-use and when-not-to-use are both spelled out.

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