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

Annotations already indicate this is a non-read-only, non-idempotent operation with destructive potential. The description adds useful behavioral detail: alerting resumes on the next missed ping, and the tool flips paused to false. 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?

Two short sentences with no filler; the core action and immediate consequence are front-loaded. Every clause earns its place.

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 state-change tool, the description covers the action, the state transition, and the alerting consequence. It doesn't state error behavior for non-paused monitors or return values, but those are minor for this simple tool, especially with a clear schema and annotations.

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 schema already documents the single id parameter at 100% coverage, so the description doesn't need to add much. It adds state-change context (paused=false) but no additional meaning for the id parameter beyond 'Monitor UUID'.

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 names a specific action ('Resume') on a specific resource ('paused LastPing monitor') and includes the exact state change (paused=false). This clearly distinguishes resume_monitor from siblings like pause_monitor and snooze_monitor.

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 clearly indicates the intended context: use when a LastPing monitor is paused, since resuming is only meaningful in that state. It doesn't explicitly name alternatives or exclusions, but the sibling list and the phrase 'paused monitor' provide clear context.

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