Workbooks Delete Workbook Schedule

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the non-obvious confirmation gate, which is real behavioral context beyond structured fields. It stops short of explaining permanence or side effects on the workbook.

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, no filler, and the destructive action is stated first with the confirmation requirement immediately after. Every sentence earns its place.

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?

An output schema exists, so return values need not be described, and annotations cover the destructive/mutation profile. However, with 0% schema parameter coverage on a destructive tool, the description omits permission prerequisites, irreversibility, and what happens to the schedule's prior exports.

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 description coverage is 0%, so the description should carry more of the burden. It clarifies the most hazardous parameter (confirm must be True), but says nothing about schedule_id or workbook_id beyond their self-evident names. Partial compensation, not full.

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 states a specific verb and resource: 'Delete a scheduled export.' This is clearly distinct from siblings like workbooks_add_workbook_schedule and workbooks_list_workbook_schedules. It does not explicitly name those alternatives, so 4 rather than 5.

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 gives one explicit precondition ('Requires confirm=True'), which is genuinely useful for correct invocation, but provides no guidance on when to delete vs. disable, no permission requirements, and no mention of alternatives. Usage is mostly implied by the name.

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