Add Issue Watcher

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

The annotations only provide destructiveHint:false, which is minimal. The description adds no additional behavioral context, such as idempotency, permissions required, or what happens if the user is already a watcher. It does not contradict the annotations, but it does not go beyond the obvious action.

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 description is a single sentence with no unnecessary words. It is perfectly concise and front-loaded.

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?

Given the tool's low complexity, the presence of an output schema, and a non-destructive annotation, the description is adequate. It states the purpose and the schema covers the rest. It does not explain permissions or error cases, but these are not essential for a simple add-watcher operation.

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?

The input schema provides 100% coverage with well-described parameters (issue_key pattern and user_identifier platform guidance). The description adds no further parameter semantics, so the baseline of 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?

The description uses a specific verb ('Add'), a direct object ('a user as a watcher'), and a clear target ('a Jira issue'). It unambiguously distinguishes this tool from sibling tools like jira_get_issue_watchers and jira_remove_watcher.

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?

The action is immediately clear from the description, leaving no doubt about when to use it. However, it does not explicitly mention exclusions or alternatives, such as 'use jira_remove_watcher to remove a watcher.' This is a minor gap, but the context is sufficiently clear.

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