Add Issue Monitor

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

Adds important behavior: 'Adding a user who is already a monitor is a no-op' and mentions return of a success confirmation object. Annotations are basic, but the description enhances understanding of idempotency for duplicates.

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 concise (5 sentences) and front-loaded with the primary action. Each sentence adds essential information: action, purpose, usage, no-op behavior, and prerequisites.

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 2-parameter mutation tool, the description covers purpose, usage, behavior, and return type ('success confirmation object'). No gaps given the 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?

While schema coverage is 100% with good descriptions, the tool description adds value by guiding how to obtain parameter values (e.g., 'use list_issues or get_issue to obtain issue IDs').

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 monitor (watcher) of a MantisBT issue,' specifying the verb 'add' and the resource 'monitor/watcher'. It distinguishes from related tools like remove_monitor and create_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?

The description explicitly says 'Use add_monitor to subscribe team members...without assigning them as handler' and directs to use remove_monitor for unsubscription. It also lists prerequisites for obtaining issue_id and username.

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