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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds important behavioral context: the deletion is irreversible, id and ping_url stop working immediately, all events are removed, and does not raise stale DOWN alerts. It also discloses the required claim_token. No contradiction with annotations.

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 front-loaded with the core purpose and consequences, then provides usage rationale and an explicit alternative. Every sentence adds distinct value, and there is no redundant or filler content.

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?

Given the tool's simplicity, the description fully covers what is deleted, why to use it, the required authentication token, irreversibility, side effects, and how to choose a non-destructive alternative. There is no output schema, but no return-value explanation is needed for a delete operation.

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 description coverage is 100%, so the schema already documents both parameters as returned by create_heartbeat. The description reinforces the necessity of claim_token but does not add substantive new parameter semantics beyond what the schema provides. 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 states a specific verb and resource: 'Permanently delete a Cronping heartbeat monitor and all its events.' It also explicitly differentiates itself from the sibling 'pause_heartbeat' by noting that pause is for temporary silencing, making the purpose unambiguous.

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 provides clear when-to-use guidance: 'tear down an ephemeral check your agent created (e.g. at shutdown, or after a one-off job)'. It also gives an explicit when-not-to-use alternative: 'To silence a check temporarily instead of deleting it, use pause_heartbeat.'

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