removeWatcher

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

The annotation readOnlyHint=false is consistent with the mutating nature of 'remove'. Beyond that, the description does not disclose any side effects, authorization requirements, or failure behaviors. It adds no behavioral context beyond what the annotation already implies, so the description carries little of the burden and provides minimal value.

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 exceedingly short, which is not true conciseness but under-specification. It lacks any structure or detail about the operation, and every meaningful piece of information is absent.

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 a nested object parameter with three required sub-fields, no output schema, and no additional context. The description fails to explain the purpose, parameters, or operational behavior, making it wholly inadequate for an agent to call 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?

Schema description coverage is 0%, so the description must compensate, but it mentions none of the parameters. It gives no hint that pathParams contains issueId, userId, or format, meaning the agent gets no help understanding what identifiers are needed or how they relate to the action.

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' provides a verb and a resource, but it is too vague to distinguish from other remove operations in the sibling list (e.g., removeUserFromGroup, removeRelatedIssue). It does not specify what a watcher is or what it is being removed from (likely an issue, given addWatcher exists), leaving the agent to infer context.

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, what prerequisites exist, or why it might be preferred over alternatives. The description gives zero context about the appropriate scenario or when not to use it.

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