Add Issue Watcher

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that restatement — it says nothing about notification side effects (adding a watcher typically emails the user), permission requirements, or what happens if the user is already a watcher.

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?

One short front-loaded sentence with zero filler. It is efficient, though the terseness borders on under-specification rather than disciplined brevity.

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?

A required output schema means return values needn't be described, and both parameters are fully documented in the schema. However, for an openWorld mutation with permission and notification implications, the description leaves out side effects and failure modes an agent would want before calling it.

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%, with issue_key showing a pattern and example and user_identifier explaining the Cloud account-ID vs Server/DC username distinction. The description adds no meaning beyond the schema, so the baseline of 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 sentence names a specific verb (add) and resource (watcher on a Jira issue), so the operation is unambiguous. It stops short of differentiating from the closely related siblings jira_get_issue_watchers and jira_remove_watcher, relying on the tool name alone for that routing.

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?

There is no guidance on when to use this versus jira_remove_watcher or jira_get_issue_watchers, and no prerequisites such as needing the issue to be visible or the caller having permission to manage watchers. Usage is only implied by the name.

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