delete_flows_flow_id

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

With no annotations provided, the description must disclose behavioral traits. It only says 'Delete Flow' without indicating whether deletion is permanent, cascading, requires authentication, or affects published flows. This is a destructive, irreversible operation with zero behavioral context.

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?

'Delete Flow' is severely under-specified, not concisely informative. It lacks necessary details and is essentially a fragment that repeats the name. It does not earn its place as a functional description.

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 operation with no annotations, no output schema, and two undocumented parameters, the one-line description is completely inadequate. It does not cover return values, side effects, prerequisites, or parameter roles, making it impossible for an agent to use correctly without external knowledge.

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?

The schema has two parameters (flowId, wabaAccountId) with no descriptions, and the tool description provides no explanation of what these parameters mean or how to use them. Schema description coverage is 0%, so the description fails to compensate.

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 'Delete Flow' simply restates the tool name delete_flows_flow_id without adding any specificity or distinguishing context. It confirms the verb and resource but provides no additional detail about the deletion scope or uniqueness compared to sibling delete tools.

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 alternatives such as delete_groups_group_id or remove_template. No scenarios, prerequisites, or exclusions are mentioned.

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