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

Goes well beyond the annotations: it spells out that omitted domains/brand names are removed, that later checks stop matching them, that already-recorded results are neither re-matched nor deleted, and that it is safe to retry. This precisely delineates the blast radius of a destructive, idempotent operation. Fully consistent with destructiveHint=true and idempotentHint=true.

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?

Front-loaded with the action and scope, then builds through the replacement rule, the consequence of omission, the confirmation step, and retry safety. Every sentence earns its place with no filler.

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 annotations carry the safety hints while the description enriches them. For a destructive bulk-replace mutation, the description covers what changes, what is destroyed, what is preserved, and the confirmation workflow.

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 6 required params, so the description must compensate. It clarifies the three content parameters and, crucially, that websiteDomains/brandNames are full-replacement lists rather than appends — a distinction the bare array schema cannot convey. The three opaque ID params remain unexplained, but their names are self-descriptive.

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 with the exact scope: replacing a competitor's name, website domains, and brand names. The full-replacement semantics sharply define the operation. It does not explicitly name or differentiate from siblings like create_competitor or delete_competitor, so it stops short of a 5.

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 a clear operational condition — pass every domain and name the competitor should keep, and show the user the full new lists before calling. It provides strong context for correct invocation but never states when to prefer this over create_competitor/delete_competitor or any exclusion.

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