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

Annotations already declare destructiveHint=true, so the safety signal is partly redundant, but the description adds real value: irreversibility, that live monitoring config is modified, and that the deleted check's last known state is returned. No output schema exists, so that return-value note is genuinely informative. It stops short of stating permission/auth requirements or downstream effects on pings.

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?

Three compact clauses, front-loaded with the irreversible action and capped with the API route and return behavior. No filler sentences.

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 destructive tool with no output schema, the definition covers what is destroyed, that it cannot be undone, the underlying API call, and what comes back. Nothing essential to calling it correctly is 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?

Only one parameter, and schema description coverage is 100% ('The check's UUID to delete.'). The description's phrase 'by UUID' merely echoes the schema and adds no format, source, or lookup guidance beyond 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?

States a specific verb (PERMANENTLY DELETES) on a specific resource (a check, identified by UUID), and the API mapping (DELETE /checks/{uuid}) removes ambiguity. It is immediately distinguishable from siblings like pause_check or update_check.

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 makes the destructive, irreversible nature clear, which implicitly gates usage, but it never names a non-destructive alternative such as pause_check or resume_check even though those siblings exist. Usage context is implied rather than stated.

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