Watch

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

Annotations already declare idempotentHint=true, openWorldHint=true, and destructiveHint=false, which cover the side-effect profile. The description adds the context that the tool sets up 'update notifications,' which is useful, but it does not elaborate on other behaviors (e.g., how notifications are delivered or how to remove the watch). No contradiction with annotations.

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, well-structured sentence that front-loads the verb and resource list. No wasted words or redundancy.

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 tool with a clear enum schema and annotations covering safety and idempotency, the description adequately explains the purpose and scope. It does not mention how to unsubscribe (watch_remove) or any prerequisites, but these are not essential for understanding this tool. The absence of an output schema reduces the need to describe return values.

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 schema has 0% description coverage, so the description should compensate. It does list the valid resource types, which matches the enum in the schema, but it gives no explanation of the 'id' parameter. Since the resource enum is self-explanatory and the tool is simple, the description provides marginal added value beyond the schema.

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 specifies the action 'Watch' and lists all supported resource types (epic, user story, task, issue, milestone, wiki page) with the purpose 'for update notifications.' It clearly distinguishes from sibling 'watch_remove' by implying an add/subscribe operation.

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 description implies usage when the user wants to receive updates on a resource, but it does not explicitly state when to use this tool versus alternatives like 'vote_add' or 'watch_remove.' No exclusions or alternative guidance is provided.

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