cancel_schedule

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

Discloses removal from schedule and daemon auto-exit when no schedules remain. With no annotations, this provides useful behavioral context. Could be improved by noting what happens on invalid schedule_id or idempotency.

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 concise sentences covering purpose, removal, and daemon behavior. No unnecessary words, front-loaded with the core action.

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?

Covers the main action and a key behavioral consequence (daemon auto-exit). Without output schema, some info on return values or error handling is missing, but sufficient for correct invocation.

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 description does not add extra meaning beyond the schema definitions. Baseline of 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?

Clearly states 'Cancel a scheduled task by ID' which is a specific verb+resource. Distinguishes from siblings like cancel_task and cancel_pipeline by mentioning 'scheduled task' and the daemon auto-exit effect.

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?

No explicit when-to-use or when-not-to-use guidance compared to siblings. The domain implies use for scheduled tasks, but does not guide the agent on selecting this over cancel_task or cancel_pipeline.

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