sigma_delete_workbook_schedule

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

Annotations already declare destructiveHint=true, so the safety profile is known. The description adds valuable behavioral info: the confirm flag must be true to execute the deletion. This is beyond what annotations provide, though it does not specify behavior when confirm is false.

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 concise sentences with zero fluff. It front-loads the action and includes the critical confirm requirement, making it an model of efficiency.

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, the description is sufficient. It identifies the necessary parameters (workbook_id and schedule_id) via schema, and the confirm gate is explicitly stated. The output schema covers return values, so no further details are needed. It misses only minor edge-case behavior.

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 must compensate. It explains the confirm parameter ('Requires confirm=True'), but workbook_id and schedule_id are only implicitly understood from the tool name and context. The description adds some meaning but does not fully document all parameters.

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 export, which is a specific verb and resource. This distinguishes it from sibling tools like sigma_list_workbook_schedules and sigma_add_workbook_schedule, making the purpose unambiguous.

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 a key usage condition ('Requires confirm=True') but does not provide explicit guidance on when to use this tool versus alternatives. While the name and context imply its use for deleting schedules, it lacks a direct reference to list or create schedule tools as alternatives.

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