watchJiraIssue

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

Annotations already disclose that this is a non-read-only, idempotent, non-destructive, open-world operation, so the safety profile is covered structurally. The description adds nothing beyond that: it does not explain the effect of watching, whether it is reversible, who is watching after the call, or any auth/rate-limit context.

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 six-word sentence with no filler and the action front-loaded. It is efficient, though for a mutating three-parameter tool the brevity edges into under-specification rather than disciplined concision.

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 state-changing tool with no output schema and a partially undocumented schema, the description is too thin: it omits the target resource type, the meaning of the toggle, permission requirements, and any note on what the call returns or how errors surface.

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 only 67%, and the description supplies no parameter meaning at all. Notably, issueIdOrKey has no schema description and is not clarified by the description, leaving the required identifier undocumented; the description could have explained the watch boolean or the accountId default but does not.

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 names a specific verb pair (watch/unwatch) and a resource (work item), so an agent can tell what the tool does at a glance. No sibling tool performs this operation, so it is distinguishable by default, though the description never says 'Jira issue' explicitly and offers no comparison to the other ~40 Jira tools.

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 statement of when to use this versus alternatives, no prerequisites (e.g., permission needed to watch), and no guidance on the toggle direction beyond the schema's own 'watch' parameter. The description only implies usage by describing the action itself.

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