removeWatcher

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it fails to mention any side effects, idempotency, permission requirements, or error handling. For a mutation tool, this is a critical gap.

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 extremely short (two words), which is under-specification rather than conciseness. It does not provide enough information for a tool with nested parameters and no other documentation.

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?

This tool has no annotations, no output schema, and a nested parameter structure, yet the description offers no context about return values, behavior on failure, or prerequisite conditions. It is wholly inadequate for an agent to invoke this tool correctly.

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 description coverage is 0%, and the description gives no additional meaning to the parameters. The pathParams object with format, issueId, and userId is explained only by their names, with no clarification of formats, relationships, or acceptable values beyond the schema enum.

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 'Remove watcher' includes a clear verb and resource, matching the tool name and suggesting the action of removing a watcher from an issue, especially given the issueId and userId parameters. It distinguishes itself from sibling tools like addWatcher, though it lacks explicit context about the target resource (e.g., 'from an issue').

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 versus alternatives, nor any prerequisites or conditions. The description is purely a statement of action without context on when it is appropriate to invoke or how it differs from similar tools like removeUserFromGroup.

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