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

The description discloses the side effects: it stops firing, sets last_published_version to 0, and preserves the definition. This aligns with the destructiveHint annotation while providing specific state changes.

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 concise, using only two sentences to convey the action, its effect, and the recovery mechanism. No unnecessary words or repetition.

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 simple single-parameter interface, the description provides all necessary context: what happens to the schedule, what is preserved, and how to resume. An agent can confidently invoke this tool based on this information.

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 only parameter, schedule_id, is fully described in the input schema with a clear explanation. The tool description adds no additional meaning beyond the schema's own description, 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?

The description clearly states the tool's function: deactivating a schedule so it stops firing. It distinguishes from related operations like delete_schedule by emphasizing that the definition is preserved.

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 explicitly notes that the definition is preserved and that republishing any version later will resume, which gives clear guidance on when to use this tool versus deleting a schedule.

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