remove_competitor

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, but the description adds genuinely new behavioral facts: a tracking slot is freed (quota effect) and history is retained rather than deleted (reversibility). These are the details an agent needs before firing a removal.

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 short sentences, front-loaded with the action and its immediate effect, then the reversibility caveat. No filler or restated metadata.

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 one-parameter removal tool with no output schema this covers what matters: what it does, side effect on quota, and that data survives. It could go further on whether dependent artifacts (leaderboard history, wins) remain accessible or whether confirmation is required.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. The description's phrase 'the same handle' loosely hints at competitor identity but does not clarify that the parameter is a numeric id rather than a handle — a mild ambiguity worth noting.

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 ('Stop tracking a competitor') that is unambiguously the inverse of the sibling add_competitor, and adds the concrete effect ('Frees the slot'). An agent can select it without opening the schema.

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?

Usage is implied through lifecycle language — 're-adding the same handle picks up where it left off' tells the agent this is reversible and that re-adding exists. There is no explicit when-to-use or when-not-to-use statement, and no named alternative (add_competitor) to route against.

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