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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description still adds real value beyond them: irreversibility ('This cannot be undone'), the precise cascade boundary, the retention of shared incidents/windows, and the `uptime.monitor.deleted` alert rule trigger as a side effect. It stops short of permission requirements or a return/error description.

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?

Everything stated is load-bearing and the irreversible warning is front-loaded after the core action. But the sentence is a run-on with an awkward comma splice ('...of this monitor only, the ones shared with other monitors are kept'), which forces a second read of the retention rule.

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 destructive tool with fully covered schema and rich annotations, the description supplies the two things annotations cannot: the cascade boundary and the downstream alerting side effect. Only permission gating and post-delete response behavior are left unstated, which are minor here.

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%, with both monitor_id and project_id documented in the schema itself. The description only restates 'by ID' and says nothing about project_id or cross-project lookup behavior, so it adds little beyond the structured fields and 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?

The description opens with a specific verb and resource ('Delete a monitor by ID') and immediately scopes the blast radius to check history, status page components, and this monitor's incidents and maintenance windows. That scope detail distinguishes it from siblings like delete_project or delete_status_page, which cascade differently.

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?

It clarifies what is removed versus retained ('the ones shared with other monitors are kept'), which implicitly supports a keep-vs-delete decision. However, it never names an alternative path such as pause_monitor for temporary stoppage, nor does it state prerequisites or when deletion is inappropriate.

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