Delete backup schedule

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

The description adds context beyond annotations by clarifying that existing backups are not deleted. However, annotations already declare destructiveHint=true, so the description reinforces but does not significantly extend behavioral insight.

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 two sentences: one for purpose and scope, one for safety. Every word is necessary, no fluff. Ideal conciseness.

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 tool's simplicity, destructive nature, and clear annotations, the description is complete: it explains what is deleted, what is not, and provides a safety instruction. No output schema exists, but the action's outcome is clear.

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 description provides no parameter documentation. One parameter (id) is undocumented in both schema and description, while the confirm parameter is explained in the schema. With 50% schema coverage, the description fails to compensate for the missing id documentation.

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 deletes a scheduled backup job, and explicitly notes that existing backups are not deleted. This distinguishes it from delete_backup and other sibling tools.

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 includes 'DESTRUCTIVE — ask the user to confirm before invoking,' providing a clear safety guideline. However, it does not explicitly state when not to use this tool (e.g., if you only want to disable but keep the job).

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