Permanently delete a cron job monitor by UUID to remove unwanted or obsolete WatchCron monitoring. This action cannot be undone.
Permanently delete a cron job monitor. This cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| uuid | Yes | Monitor UUID to delete |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does disclose the single most important trait: the deletion is permanent and irreversible. It omits other relevant behavior an agent would want before a destructive call, such as what happens to associated pings/incidents or whether an active monitor must be paused first.
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 with zero waste, and the irreversible nature is front-loaded where an agent will see it before acting.
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 one-parameter delete tool with a fully documented schema and no output schema, the definition covers purpose and the critical irreversibility warning. Only secondary details about side effects on related data are missing.
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% for the single 'uuid' parameter, which is already documented as 'Monitor UUID to delete.' The description adds no syntax, format, or sourcing detail beyond the schema, 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 and resource: 'Permanently delete a cron job monitor.' The adverb 'permanently' implicitly separates it from pause_monitor, but no sibling is named explicitly, so the differentiation is left to inference.
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?
There is no statement of when to use this versus alternatives such as pause_monitor or update_monitor, and no prerequisites or exclusions. The 'cannot be undone' warning signals caution but is not usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.