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

Goes well beyond the annotations: it explains that this is a soft delete, that member agents and queues stop dispatching and vanish from listings, that underlying rows and run history are preserved rather than erased, and that in-progress runs are interrupted. That is exactly the destructive-scope detail an agent needs before invoking a destructiveHint=true tool, and it is fully consistent with the annotations.

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, each earning its place: the action front-loaded, then the visibility/dispatch effects, then the data-preservation and run-interruption caveats. No filler or restatement of the title.

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 single-parameter mutation with annotations covering destructiveness, idempotency and open-world scope, and with no output schema, the description supplies nearly everything needed. The only gap is post-delete behavior an agent might wonder about, such as whether the automation can be restored or what a repeat call returns.

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?

Only one parameter (automation_id) with 100% schema description coverage, so the schema already carries the semantics. The description adds no information about where the ID comes from (e.g., listAutomations) or what happens with an invalid or already-deleted ID, so the baseline 3 applies.

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 ('Soft-delete an automation'), and the qualifier 'soft-' meaningfully distinguishes it from hard-delete siblings like deleteAgent or deleteQueue. Sibling differentiation is implicit through the resource name rather than stated explicitly, and no alternative tool (e.g., updateAutomation to disable) is referenced.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative such as updateAutomation or deleteAgent for adjacent cleanup tasks. Usage is only implied by the described consequences (listings disappear, runs interrupted), which a careful agent can infer from but which falls short of routing guidance.

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