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

Annotations declare a non-read, idempotent, non-destructive mutation; the description goes well beyond them by disclosing that the list is fully replaced (not appended), that aliases count as naming the competitor in past weeks' answers, and that names are trimmed, deduplicated, self-name-stripped, and that an empty list resets to name-only. These side-effect details are exactly what annotations cannot convey.

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, no filler. The replacement/limit fact is front-loaded, behavioral edge cases follow, and the affinity links sit at the end where they belong.

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 two-parameter mutation with a full output schema, the description covers the mutation semantics an agent needs. It is slightly thin on practical details such as what happens if more than 5 aliases are supplied or whether the update takes effect immediately in scoring, but nothing critical 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics the schema lacks: the maximum of 5 aliases, the normalization rules applied to each entry, and the empty-list reset behavior. It does not restate the schema's own example format, but the added constraints are meaningful.

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 ('replaces') plus the exact resource ('a competitor's other names') and even the cardinality limit (up to 5). An agent can immediately distinguish this from list_competitors or get_competitor_scorecard, which are read operations.

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?

The 'Related: list_competitors, get_competitor_scorecard' line hints at the workflow (get the id, then set aliases), but it never states when to use this versus alternatives such as track_competitor or untrack_competitor. Usage is implied rather than prescribed.

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