Remove competitor

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

Annotations already declare destructiveHint=true, but the description adds nothing beyond the one-line action statement. It doesn't explain irreversibility, whether related data (saved views, alerts, signals) is affected by removal, or whether idempotent re-calls fail. For a destructive tool the description should expand on consequences; it doesn't.

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?

One terse sentence that states purpose without filler. Efficient and front-loaded. No wasted words.

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 destructive mutation tool with no output schema and minimal annotations, this is under-specified. It doesn't clarify what happens to associated tracked data, whether the operation is idempotent, or what error conditions apply (e.g., removing a nonexistent competitor). The incomplete idempotency_key documentation also reduces completeness.

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 67%: project_id and competitor_id have descriptions, but the optional idempotency_key has none. The description adds no semantics beyond the schema. Baseline 3 is reasonable since the two required params are documented; the idempotency_key remains undocumented.

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 clearly states the verb ('Remove') and resource ('a tracked competitor'), with scope ('from a project'). It distinguishes from siblings like add_competitor and list_competitors, though it doesn't explicitly mention those alternatives. It's clear but not maximally differentiated.

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?

No guidance on when to use this tool versus alternatives, no prerequisites mentioned (e.g., competitor must exist, project must exist), and no effects described (e.g., whether this permanently deletes the competitor or just removes tracking). With destructiveHint=true and no explanation, an agent has no context on consequences.

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