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

Annotations indicate a write operation (readOnlyHint=false) that is not destructive (destructiveHint=false), and the description adds meaningful behavior beyond those flags: paused schedules 'keep their place but never fire until resumed' and a logged-in identity is required. This clarifies persistence semantics and an auth prerequisite without contradicting the 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?

Three short sentences, each with distinct value: the action, the pause behavior, and the auth requirement. There is no filler, redundant restatement of the schema, or unnecessary elaboration.

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 two-parameter boolean toggle with full schema coverage and annotations, the description supplies the key behavioral consequences and prerequisite. It omits return/confirmation details, but no output schema exists and the semantics are simple enough that this is a minor gap.

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%, with schedule_id and paused both fully described, including the boolean semantics ('true to pause, false to resume'). The description does not add field-level detail, but at this coverage the schema already carries the burden, so baseline 3 is appropriate.

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 the exact operation ('Pause or resume') and resource ('your rig schedules'), so there is no ambiguity about what the tool does. It also scopes the action to existing user-owned schedules, which distinguishes it from siblings like schedule_create, schedule_delete, and schedule_list.

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 provides a clear context: use this to toggle an existing schedule between paused and active, with the consequence that paused schedules never fire until resumed. However, it does not explicitly name alternatives or state when pausing is preferable to deleting, so the agent must infer the boundary from sibling tool names.

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