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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description earns credit by specifying WHAT is destroyed: all: true 'stop and forget everything,' and stop_alerts only silences Slack/Discord alerts rather than removing the watch. That distinction between data deletion and notification muting is not derivable from the 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?

A single sentence, front-loaded with the verb and resource, wasting no words. The inline colon-separated flag explanations are dense but readable; minor cost is slight run-on structure.

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 exists, so return values need no explanation, and the destructive scope is covered. What remains missing is whether all: true is exclusive with packages/companies and what happens to a watch that was only alert-muted.

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 0% across 4 parameters, so the description carries the burden. It explains the semantics of all and stop_alerts well, but packages and companies are left entirely undefined (accepted identifier format, interaction with all: true), leaving half the parameters 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?

States a specific verb and resource ('stop watching packages or companies') and is clearly the inverse of the sibling koot_watch. The 'PRO.' prefix adds a tier marker but the core purpose is unambiguous 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?

It distinguishes two modes of use (all: true for full removal vs stop_alerts: true for muting notifications), which is genuine usage guidance. However it never says when to prefer unwatch over alternatives like koot_watches management, nor any prerequisites or exclusivity rules between the flags.

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