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

Annotations already indicate mutating, non-destructive, idempotent behavior. The description adds valuable behavioral context beyond that: 'While paused, missed pings are ignored and no alerts fire' and that resuming re-arms the dead-man's-switch. This clearly explains the operational effect without contradicting any annotation.

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 four sentences with every sentence earning its place: the core action, the use case, the behavioral effect, and the required prerequisite. It is front-loaded with the most important information and contains no filler.

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 three-parameter mutation tool with no output schema, the description is complete. It explains what the tool does, when to use it, what happens while paused, and what credential is required. No important calling context 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?

Schema coverage is 100%, so the schema already fully documents id, paused, and claim_token. The description adds the semantic link that claim_token comes from create_heartbeat and that paused controls pause vs. resume, but it does not go beyond the schema's own parameter descriptions.

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: 'Pause or resume monitoring on an existing Cronping check without deleting it.' It clearly distinguishes itself from delete_heartbeat by emphasizing the check is not deleted, and the behavior of pausing versus resuming is immediately understandable.

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 gives explicit when-to-use guidance: 'Pause during planned maintenance or a known downtime window so a silent job does not raise a false DOWN alert; resume to re-arm the dead-man's-switch.' It also specifies the prerequisite claim_token, making it clear when the tool is applicable.

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