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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes further and discloses the exact blast radius: historical snapshots and detected changes are deleted via cascading delete, with no archive retained. That is precisely the kind of consequence an agent needs before invoking a destructive tool.

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 sentences, zero filler. The action is front-loaded in the first clause and the destructive consequence plus the differentiation follow immediately.

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 tool with no output schema, everything an agent needs is present: the action, the cascading data loss, and the contrast with rank tracking. Annotations carry the safety profile and the schema carries the parameters.

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 (targetId, projectId) are documented with their sources, so the description does not need to explain them. It adds only the implicit 'one competitor URL' scoping, so the baseline 3 is appropriate.

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 ('Stops monitoring one competitor URL') and contrasts it with the rank-tracking equivalent, so an agent can distinguish it from add_competitor_monitor and list_competitor_monitors 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 rather than stated: the tool is clearly the removal counterpart to add_competitor_monitor, and the rank-tracking contrast hints at the data-loss trade-off. However, it never explicitly says when to use this versus alternatives (e.g. delete_brand_monitor for brand monitors) or any preconditions.

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