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

The description does add real behavioral context beyond annotations: the assignee and reporter keep receiving emails unless they change their notification settings, which clarifies the scope of the effect. However, it repeats 'idempotent' three times even though idempotentHint=true already declares it, and it never explains what the declared destructiveHint=true actually affects (the watcher entry).

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?

The same statement is made twice almost verbatim ('Stop watching the issue (idempotent; spec D92)' and 'Stop watching (idempotent)'), and 'spec D92' is an internal reference with no meaning to an agent. Roughly half the text is redundant padding.

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 simple two-parameter mutation, the annotations already carry the safety profile (destructive, idempotent, not read-only) and the schema carries the parameters. The description contributes the notification-behavior caveat, which is genuinely useful, but omits what state actually changes and how to undo it via watch_issue.

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 (project_key, issue_key) are fully documented with patterns and examples in the schema. The description adds nothing about parameters, which is acceptable given the schema does the work, so 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 first sentence states a clear verb+resource ('Stop watching the issue'), which is unambiguous and implicitly the inverse of the sibling watch_issue. It does not explicitly name watch_issue or otherwise differentiate itself, so it falls short of a 5.

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 only implied: the agent infers you call this when you no longer want notifications for an issue. There is no explicit 'use this instead of X', no prerequisites, and no mention of the counterpart watch_issue for re-subscribing.

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