jira_add_watcher

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

With no annotations, the description carries the full burden. It only states the action without disclosing reversibility, authorization needs, idempotency, or side effects like notifications. The description is insufficient for behavioral transparency.

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 concise sentence that is front-loaded and contains no fluff. However, it could be slightly more informative without sacrificing brevity, such as indicating that the user will start watching the issue.

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 simplicity, the description is minimally adequate. It does not explain the return value or any prerequisites. With no output schema, the agent lacks information on success indicators. Sibling tools suggest a related workflow, but the description does not address this.

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 coverage is 100%, so the schema already documents both parameters. The description adds no extra meaning beyond the schema (e.g., format of issueKey or how to obtain accountId). Baseline 3 is appropriate as the description does not detract.

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 clearly states adding a watcher to a Jira issue. The verb 'Add' and resource 'watcher' are specific, and the tool name distinguishes it from siblings like jira_remove_watcher and jira_get_watchers. However, it lacks explicit differentiation or context about watchers.

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?

No guidance is provided on when to use this tool compared to alternatives. For instance, it does not suggest checking if a user is already watching via jira_get_watchers or mention required permissions.

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