delete_all_schedules

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

No annotations are provided, so the description carries full burden. It does disclose the key trait that the action is permanent and affects ALL schedules, which is meaningful. However, it omits confirmability, reversibility, auth requirements, and any return/error behavior for a mass-destructive operation.

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, front-loaded with the action and scope, followed by a caution. No filler.

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 bulk destructive tool with no annotations and no output schema, the description covers the fundamental facts (permanent, deletes all) but lacks safety framing such as confirmation expectations or permission requirements. Adequate but thin given the destructive nature.

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 tool has zero parameters, so there is nothing to document; baseline 4 applies. The description correctly implies no filtering or scoping arguments.

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 ('delete') and resource ('ALL scheduled job discovery cron jobs') with an explicit 'ALL' scope. It is distinguishable from the sibling 'delete_schedule' (singular) by the 'ALL' qualifier, though it never names that sibling explicitly.

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?

Provides only 'Use with caution' as guidance, with no when-to-use condition, no mention of when to prefer the singular 'delete_schedule', and no prerequisites. The agent must infer everything about routing.

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