delete_flow

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

The description discloses the destructive nature through the verb 'delete' but provides no additional context about side effects, irreversibility, permissions, or impact on related data. With no annotations present, the description carries the full burden and fails to add meaningful behavioral detail.

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 description is concise and well-structured, with a clear one-line purpose and an Args/Returns breakdown. It is front-loaded and wastes no words, though it may be too terse to be fully informative.

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?

The description is insufficient for a complete understanding of the tool. It lacks usage guidelines and behavioral transparency. Although the tool is simple and has an output schema, the description does not cover important aspects like when to use or safety considerations, making it only partially complete.

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 description restates the parameter name (flow_id) as 'Flow ID to delete', which adds minimal semantic value beyond the schema's bare string type. Since schema coverage is 0%, the description should compensate with richer meaning, but it merely echoes the parameter name without explaining constraints or context.

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 a flow' uses a specific verb and resource, clearly indicating a destructive operation. It distinguishes from sibling tools like update_flow, patch_flow, and create_flow by the explicit delete action.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or comparison with other flow-related tools, leaving the agent to infer usage solely from the name.

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