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

Annotations declare destructiveHint=false, which could be surprising for a delete tool. The description clarifies this by stating 'Does not touch anything it already started,' explaining that past actions are unaffected. It also discloses the required authentication scope, adding value beyond the annotations. No contradiction is present.

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 two concise sentences. The first states the core purpose, the second adds crucial clarification about side effects and requirements. It is front-loaded with the action and includes no extraneous information.

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 one-parameter delete operation, the description covers the effect, what is not affected, and the required scope. It omits error handling or idempotency details, but these are minor for this simple tool and are not essential for correct invocation.

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%, with monitor_id fully described as 'The monitor's id, from create_monitor or list_monitors.' The description adds no additional parameter-level detail, so the baseline of 3 is appropriate since the schema already covers it.

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: 'Delete one of your standing watches, so it stops firing.' This is a specific verb and resource, and it distinguishes from siblings like create_monitor and list_monitors. It immediately conveys what the tool does without ambiguity.

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 implies when to use it: when you want to stop a standing watch. It also adds a prerequisite ('Requires authentication and the monitors:write scope') which guides usage. However, it does not explicitly mention alternatives or when not to use it, but given the context of create/list monitors, the intent is clear.

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