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

With no annotations at all, the description carries the full disclosure burden and does well: it identifies exactly which actions are destructive (delete_flow, delete_folder) and imposes a human-confirmation gate before them. It stops short of stating irreversibility, permission requirements, or what happens to flows/campaigns that reference a deleted flow.

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?

Two sentences with no waste: the scope of actions comes first and the safety constraint second. The most consequential information (destructive actions need confirmation) is stated plainly and early.

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 6-parameter, 5-action mutation tool with no annotations and no output schema, the description covers the destructive path but merely names create_folder, rename_folder, and merge_duplicate_folders without explaining their behavior or results. It leaves the agent to guess at merge semantics and what a successful response looks like.

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%, so the schema already documents every parameter including the action enum and the confirm precondition. The description's mention of confirm=true largely restates the schema, adding no syntax, defaults, or edge-case semantics (e.g., how flowIdentifier resolves names vs IDs).

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 ('Deletes a conversation flow') and enumerates the sibling folder actions (create_folder, rename_folder, delete_folder, merge_duplicate_folders). This clearly separates it from create_flow, clone_flow, update_flow, and trigger_flow, though it doesn't explicitly say why folder management lives here rather than in update_flow.

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?

It gives a concrete usage rule — destructive actions require confirm=true after explicit user confirmation — which is genuinely actionable. However, it never states when to use this tool versus update_flow/create_flow/clone_flow, or when merge_duplicate_folders is appropriate over delete_folder, leaving action selection to inference from the enum.

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