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

Annotations already declare destructiveHint=true, non-idempotent, and non-read-only, so the safety profile is covered. The description adds a genuine behavioral detail beyond that: unknown app IDs are reported without altering tracking, hinting at partial-failure semantics. It remains slightly ambiguous whether the whole operation is skipped or just the unknown IDs.

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 tight sentences, action front-loaded, no redundant restatement of the title or name. Every clause carries information.

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?

An output schema and annotations cover return values and safety, and the unknown-ID note addresses one failure mode. But for a destructive, non-idempotent mutation with two undocumented parameters, the description is thin on which IDs apply and how to select the store.

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 only 33%, so the description should compensate but it adds no parameter meaning. It never mentions appIds (the things being removed, 1-50 items) or projectId, and does not mention storeProvider's default behavior, which only appears in the 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?

States a specific verb and resource (removes competitor apps) plus a scope qualifier ('in one store') that implies storeProvider selection. It clearly implies the inverse of add_keyword_competitors, but never names that sibling to make the distinction explicit.

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 versus add_keyword_competitors, remove_keywords, or list_keyword_competitors, and no prerequisite context. The only usage-adjacent hint is the store-scoping phrase, which is incidental rather than instructional.

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