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

Annotations already declare destructiveHint=true, but the description adds meaningful context beyond them: permanence ('for good'), the safer soft-delete alternative, and the fact that the call may return `needs_confirmation` (which pairs with the approvalId parameter). It stops short of describing idempotency or side effects on dependents, so it's strong but not exhaustive.

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 short sentences, front-loaded with the core action and permanence, then the alternative, then the confirmation caveat. No filler; every sentence carries a distinct decision-relevant fact.

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?

No output schema exists, so the description carries the return burden and handles it by flagging `needs_confirmation` and tying it to approvalId. For a destructive mutation with a confirmation round-trip this is nearly sufficient; it could still note what happens to a running schedule or in-flight executions.

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 100%, so flowId, scheduleId, workspace, and approvalId are all documented in the schema itself. The description hints at the confirmation flow (approvalId) but adds no syntax or value details beyond what the schema already provides, matching the baseline of 3.

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 and resource ('Removes a schedule') with the permanence qualifier ('for good'), clearly distinguishing it from the sibling update tool. An agent can tell what this does and how it differs from workbench_flows_schedules_update without opening the schema.

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?

Explicitly names the alternative (workbench_flows_schedules_update with enabled: false) and the exact condition that selects it ('when the user might want it back'). This is a textbook when-not-to-use-the-destructive-tool guidance.

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