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

No annotations are provided, so the description carries the full behavioral burden. It states the mutation but omits the critical traits of a delete operation: whether deletion is permanent or reversible, what happens to existing runs/history, and whether any permissions or confirmations are required.

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 single sentence is front-loaded and free of padding, but the brevity reflects under-specification rather than efficiency. There is no structure to convey scope, side effects, or prerequisites.

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?

For a destructive single-parameter tool with no annotations and no output schema, the definition is substantially incomplete. An agent cannot confirm irreversibility, side effects, or parameter meaning from the description alone.

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%, and the description never mentions schedule_id — it does not say what identifier is expected, where to obtain it, or what happens if it is invalid. With one undocumented parameter, the description should have compensated but does not.

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 gives a specific verb ('Delete') and resource ('an automation'), so the operation is clear at a glance. It offers no differentiation from sibling operations such as schedule_update, schedule_get, or the pipeline/storage delete tools, and the term 'automation' does not exactly match the tool name 'schedule'.

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?

There is no guidance on when to use this tool versus schedule_update, schedule_export, or pipeline_delete, and no prerequisites or confirmation requirements are mentioned. The agent must infer usage entirely from the name and the single required parameter.

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