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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds material context beyond them: it is a WRITE operation requiring an Indie plan (trial counts) and an authorized account or write-scoped API key, which is useful permission/auth information an agent cannot derive from annotations alone.

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?

Two compact sentences with the mutation flag and the action front-loaded, followed by requirements. No filler, no repetition of schema content.

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 destructive mutation with full schema coverage and annotations covering the safety profile, the description supplies the missing pieces (auth, plan tier, write scope). With no output schema required and IDs documented in the schema, nothing an agent needs to invoke this correctly is absent.

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 100% and both parameters are documented with UUID guidance and pointers to sonar_list_products/sonar_create_product, including the explicit warning that competitor_app_id is the app UUID and not a store id. The description adds nothing further about the parameters, so the baseline 3 applies.

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 names a specific verb and resource: 'remove a competitor from a product in the caller's Sonar workspace', and the 'WRITE tool' prefix immediately flags it as a mutation. It is clear what the tool does, but it never contrasts itself with the adjacent competitor tools (sonar_track_competitor, sonar_scan_competitor, sonar_analyze_competitors), so the removal-vs-tracking boundary is left to inference.

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 supplies prerequisites (Indie plan, authorized account or API key with write scope) rather than when-to-use guidance. There is no statement of when to pick this over tracking/untracking a competitor or scanning it, so usage is only implied by the verb.

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