Remove Issue Monitor

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the mutation/irreversibility profile is covered. The description adds the useful consequence that the user stops receiving email notifications, but it does not mention permission/auth requirements or whether the monitor must first exist, so it goes modestly beyond annotations.

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?

Two tight sentences with the action front-loaded and the consequence second; nothing is redundant. It is appropriately sized for a simple two-parameter tool.

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 two-parameter mutation whose safety profile is fully covered by annotations and whose parameters are fully documented in the schema, the description gives enough to call it correctly. Only the absence of sibling routing and permission details keeps it from being fully complete.

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 100% – issue_id and username are both documented in the schema with types and constraints. The description adds no format or edge-case detail about the parameters, so the baseline 3 applies.

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?

States a specific verb (Remove) and resource (user from the monitor list of a MantisBT issue), and the second sentence clarifies the effect. It is clearly distinguishable from read-oriented siblings, though it never names its natural counterpart add_monitor to sharpen the distinction.

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 says what the tool does but provides no when-to-use or when-not guidance and no reference to the sibling add_monitor that is its direct inverse. An agent must infer the triggering context entirely.

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