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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's 'Permanently ... cannot be undone' reinforces rather than pioneers. It does add value beyond annotations by disclosing the authorization requirement ('Only the owner can delete a flow') and describing the success response shape.

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?

Four short sentences with zero filler, and the irreversible consequence is front-loaded immediately after the purpose. Because no output schema exists, the return-value sentence earns its place rather than repeating structured data.

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 the essentials for an irreversible mutation: what is destroyed, who may do it, and the return payload, with no output schema available to carry the latter. It stops short of noting cascade effects (collaborators, folder membership, active shares) that an agent might reasonably wonder about.

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% with a single parameter whose schema text ('The id of the flow to delete') is fully self-explanatory. The description's 'by id' adds no syntax, format, or sourcing detail beyond the schema, so 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 (delete), resource (saved Wavelength flow), identifier (by id), and a distinguishing scope. Among siblings like delete_folder, delete_organization, and delete_portal, the resource named here makes the target unambiguous.

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?

The owner-only constraint functions as a prerequisite, which is useful usage guidance. However, there is no explicit when-to-use vs. alternatives guidance (e.g. delete_folder vs. delete_flow, or restore_version for recovery); usage is implied by the resource name.

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