Delete Uptime Kuma Monitor

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

The description explicitly discloses that the operation is destructive, irreversible, and deletes heartbeat history as well as the monitor. This goes beyond the destructiveHint annotation by specifying exactly what is destroyed and that confirmation is required. No contradiction with annotations exists.

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 extremely compact and front-loads the most critical fact (destructive deletion plus heartbeat history). The Args block is minimal and every sentence contributes useful 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 single-parameter deletion tool with full schema coverage and annotations covering the safety profile, the description provides everything needed: the target, the side effect, the irreversibility, and the confirmation requirement. No output schema exists, so no return-value details are required.

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?

The input schema already fully documents monitor_id with a description and minimum value, and schema description coverage is 100%. The description merely repeats the parameter with '(int)', adding no meaningful semantic detail beyond the schema.

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 states a specific verb and resource: 'Delete a monitor and its heartbeat history.' This clearly differentiates the tool from siblings like pause, resume, or edit by explicitly naming the destructive scope and the data affected.

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 usage is implied by the tool name and description, but there is no explicit guidance on when to choose delete over alternatives like pause or edit. The 'Requires confirmation' note is a workflow prerequisite, not a comparative usage guideline.

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