Delete Standard Flow

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

Annotations already indicate destructiveHint=true. The description adds 'Cannot be undone', explicitly stating irreversibility, which is not in the annotations. However, it does not disclose other behavioral aspects like authorization or effects on dependent objects.

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 consists of one concise sentence with no redundant words. It is front-loaded with the key action. However, it could be slightly more informative while remaining concise.

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?

Given the sibling 'delete_advanced_flow', the description does not clarify the difference between standard and advanced flows. It lacks information on preconditions, post-conditions, or dependencies. The tool is simple, but more context would improve completeness.

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 input schema has 0% description coverage for the 'id' parameter. The description merely says 'by ID' without specifying the ID format, example, or source. It adds minimal meaning beyond the schema's type constraint.

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 clearly states the verb 'delete', the resource 'standard Flow', and the parameter 'by ID'. It distinguishes from sibling 'delete_advanced_flow' by specifying 'standard'.

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 description mentions permanence ('Cannot be undone'), implying careful use, but does not explicitly state when to use this tool versus alternatives like 'delete_advanced_flow'. It provides minimal guidance beyond the destructive nature.

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