Add Issue Monitor

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

Discloses that adding an existing monitor is a no-op and explains email notification behavior. Annotations confirm mutation but not destructiveness; description adds useful context without contradiction.

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?

Concise and well-structured: three short paragraphs with front-loaded purpose, clear usage guidance, and prerequisites. Every sentence adds value.

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?

Covers prerequisites, behavior, and return type (success confirmation). Lacks detailed return schema but adequate for a simple add operation. No output schema exists, so minimal return info is acceptable.

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 coverage is 100% and parameter descriptions are already detailed. The description reiterates prerequisite lookup methods but does not add new semantic meaning beyond the 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 clearly states the tool adds a user as a monitor/watcher for a MantisBT issue, including that monitors receive email notifications. It distinguishes from sibling tools like remove_monitor.

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?

Provides explicit guidance: when to use (subscribe without assigning), alternative (remove_monitor), and prerequisites (obtain issue_id from list_issues/get_issue, look up usernames via find_project_member/get_project_users).

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