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

Beyond the destructiveHint=true annotation, the description discloses the nuanced write semantics: omission preserves vs null clears, null/[] clears identifier groups, tracked=false keeps the entry re-enableable, rename refuses duplicate or blank names and preserves identity/history, unknown resets type. It also names side effects (null return on remove, scanConfig returned) and a recovery path if identity setup is incomplete.

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?

Purpose and preconditions are front-loaded, and nearly every clause carries a distinct semantic (null vs omission, rename rules, repair workflow). It is dense to the point of being a run-on paragraph and 'all three identifier groups' is mildly jargonistic, but little is truly wasted.

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 13-parameter destructive tool with an output schema, the description covers prerequisites, per-field mutation semantics, identity selection, side effects, non-effects, and an error-recovery path. Nothing essential to invoking or recovering from the call is missing.

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?

With only 46% schema description coverage and 13 parameters, the description compensates heavily: it explains the preserve-vs-clear contract for name/domain/description/subtype/context and identifier groups, that required name/type/tracked cannot be null, and that competitorId doubles as a saved roster row id for repair. This adds meaning well beyond the sparse schema.

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 opens with a specific verb+resource (edit competitor details, identifiers, tracking) and immediately scopes it to 'Site competitors and Topic entities, which need not be rivals.' It is clearly distinguishable from add_competitor and remove_competitor, and even states what the tool does not do (no publication or Scan launch).

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?

It states the preconditions explicitly: exactly one configured identity or legacy row ID, and at least one editable field. It also gives a concrete repair workflow ('read list_competitors and repair with update_competitor using competitorId... do not duplicate the add'). It does not, however, explicitly route to sibling alternatives for the normal case, so it falls short of a 5.

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