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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description still earns credit by disclosing blast radius beyond the annotations: in-flight runs are untouched while dependent schedules are broken until the workflow is re-saved. It stops short of stating auth requirements or whether a missing name errors versus no-ops.

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 sentences, zero padding, with the destructive nature front-loaded and the consequence detail immediately after. Every clause carries information an agent needs before calling.

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, and the description does not say what a successful call returns or how a nonexistent workflow is handled. Otherwise, for a one-parameter destructive tool whose annotations already flag destructiveness, the side-effect disclosure makes it callable without further reading.

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?

Single required 'name' parameter at 100% schema description coverage, so the schema already carries the semantics. The description adds nothing about the parameter (e.g., whether name is case-sensitive or accepts an ID), which is acceptable at this coverage level but not additive.

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?

Names a specific verb and resource ('Permanently delete a saved workflow') and is trivially distinguishable from the sibling delete_schedule by resource type. The adverb 'permanently' also signals this is not a soft-delete or archive operation.

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?

Usage is only implied: the stated consequences (schedules stop starting runs) let an agent infer this is the right call when retiring a workflow, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g., save_workflow to overwrite, or disabling a schedule).

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