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

Annotations already declare it is a non-destructive, idempotent mutation; the description adds genuinely new behavior: a recurring schedule resumes at its next cron time, while a one-time schedule requires a future run time. That is real operational context beyond the hints, though it omits what error or resulting state occurs when the one-time run time is already past.

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 short sentences with zero padding; the action is front-loaded and the two schedule-type caveats follow in priority order.

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, non-destructive, idempotent mutation with a fully documented schema and no output schema, the description covers the essentials including the failure precondition. It is only slightly thin on what the agent should do if the one-time run time has passed.

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% and the id parameter already documents its source ('from schedule_request or list_schedules'). The description adds no additional meaning about the id or any format constraints, so the baseline of 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?

States a specific verb ('Resume') plus the exact resource and required prior state ('a paused request'), which cleanly separates it from pause_schedule and delete_schedule in the sibling list. An agent can identify the operation without opening the schema.

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 precondition (must be paused) and the schedule-type-dependent outcome give clear context for when to call it and when the call will not succeed. It does not explicitly name pause_schedule or list_schedules as the counterpart/verification steps, so it stops short of full when/when-not routing.

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