redmine_add_watcher

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

The description reveals that the tool is idempotent on the Redmine side and honors the REDMINE_MCP_READ_ONLY flag. Since no annotations are provided, this behavioral information is valuable and goes beyond what the schema offers.

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 concise and well-structured: a clear one-sentence purpose, blank line, then parameter descriptions and additional behavioral notes. Every sentence adds value without unnecessary verbosity.

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 two-parameter tool, the description covers purpose, parameters, idempotency, and read-only behavior. With an output schema present, return values are not needed. However, it does not mention error behavior (e.g., if issue not found) or authentication requirements.

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 description clearly explains both parameters: 'issue_id' as 'numeric Redmine issue id' and 'user_id' as 'numeric user id to add to the watcher list'. This adds meaning beyond the schema's titles and compensates for the 0% schema description coverage.

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 'Add a user as a watcher of an issue', specifying the verb 'add', the resource 'watcher', and the context 'issue'. This distinguishes it from sibling tools like 'remove_watcher' and 'list_watchers'.

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 mentions idempotency and read-only mode but does not provide explicit guidance on when to use this tool versus alternatives. It relies on the name and basic description to imply usage context. No 'when not to use' or alternatives listed.

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