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

Annotations already declare destructiveHint=true, idempotentHint=true and non-read-only, so safety is covered. The description adds genuine value beyond them by clarifying exactly what is destroyed (only the status-page association, not the monitor) and that monitoring continues, which is the key risk an agent would otherwise misjudge.

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 short sentences, the action first and the critical non-destructive nuance second. Zero filler.

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 with rich annotations and no output schema, the description covers what the agent needs to act safely. Minor gaps remain: error behavior if the monitor is not on the page, and that the action can be undone via the add tool.

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?

Both parameters (id, monitorId) are fully documented in the schema at 100% coverage, so the baseline is 3. The description adds no format, ordering, or failure semantics for either parameter, so it neither helps nor hurts.

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?

Names a specific verb and resource (remove a monitor from a status page) and immediately scopes it against the obvious confusion case by stating the monitor itself is not deleted. An agent can distinguish this from vs_monitors_delete or vs_status_page_monitors_add without opening any schema.

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 scope clarification ('the monitor itself is not deleted and keeps checking') effectively tells the agent when to pick this over deleting a monitor, and the name implies the add/remove pairing. It stops short of naming the sibling tools explicitly (e.g. vs_status_page_monitors_add for reversibility), so no explicit exclusions.

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