redmine_remove_watcher

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

With no annotations, the description carries full burden. It discloses important behavioral details: error semantics (404 meaning watcher not on list vs issue not found) and honors a read-only flag ('REDMINE_MCP_READ_ONLY'). This adds valuable 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?

The description is succinct and front-loaded with the main purpose. Every sentence serves a purpose: the one-liner for action, the args listing, and the error/flag note. No wasted words.

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 removal tool with two parameters and no nested objects, the description covers the main purpose, parameter types, error handling, and a read-only mode. The output schema exists but is not shown, so return values are not described. Still, the description is largely complete for the tool's complexity.

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. It provides brief explanations for each parameter ('numeric Redmine issue id', 'numeric user id to remove'), which adds basic meaning but lacks constraints or additional context. This meets the baseline but does not excel.

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 clearly states the action ('Remove a user from an issue's watcher list') with a specific verb and resource. It distinguishes itself from sibling tools like 'redmine_add_watcher' and 'redmine_list_watchers' by name and action.

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 clearly indicates when to use this tool (to remove a watcher), and the sibling list provides context. However, it does not explicitly state when not to use it or mention alternatives beyond the tool name.

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