addWatcher

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

The annotation readOnlyHint=false indicates mutation, and 'Add' implies a write operation, so there is no contradiction. However, the description discloses nothing beyond the bare action—no mention of side effects, authorization requirements, idempotency, or error behavior.

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 minimal but not effectively concise—it omits necessary context. A single sentence can be concise and informative, but 'Add watcher' is under-specification rather than efficient communication.

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?

The tool has nested parameters, no output schema, and no enrichment from annotations beyond the mutation hint. The description does not explain what is being modified, how parameters relate, or what the caller should expect, leaving the agent to infer critical details from parameter names.

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 0%, so the description carries the full burden for explaining parameters. It does not clarify that bodyParams.user_id is the user being added or that pathParams.issueId identifies the target issue. The description adds no value over the raw 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 'Add watcher' is essentially a restatement of the tool name, providing no additional meaning. It does not state that the watcher is added to an issue, which would require consulting the schema to infer from the 'issueId' path parameter.

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 tool versus alternatives like removeWatcher. The description does not mention any context, prerequisites, or scenarios where adding a watcher is appropriate.

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