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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description goes well beyond them: it specifies that only the cron schedule is removed while the saved workflow definition survives, gives the recovery path (re-save via `schedule_task`), and documents success/error return behavior. For a destructive tool, disclosing the exact scope of destruction and what is preserved is exactly the added value needed.

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?

Purpose is front-loaded in the first sentence and the body earns its place with scope and return details. The phrasing around workflow schedules ('the value `schedule_task` returned as `task_name`') is slightly convoluted and could be tightened, but nothing is wasted.

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?

Covers purpose, name-source convention, blast radius, recovery path, and return/error behavior, and an output schema exists for the response shape. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds cross-tool semantics the schema alone does not: for workflow schedules `task_name` is the value returned by `schedule_task` as `task_name`. This resolves real ambiguity about which identifier to pass.

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 (scheduled task / cron job) plus the identifier used to select it. It is immediately distinguishable from the many sibling delete_* tools (delete_event_subscription, delete_saved_query, delete_user_template) because the resource is named 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?

Clarifies the key selection consideration for workflow schedules and frames the operation as removable/re-creatable via `schedule_task`, which is genuinely useful routing context. It does not, however, state any explicit when-not-to-use condition or prerequisites (e.g. permissions, effect on running jobs).

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