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

The annotations already establish that this is a non-read-only, non-idempotent, non-destructive create operation, lowering the disclosure burden. The description adds useful context that the scheme is reusable and can be applied to campaigns later, but it does not describe permissions, side effects, validation behavior, or response details.

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 short and front-loads the purpose before giving the flows payload shape. The second sentence is dense and uses an ellipsis, but there is little unnecessary wording.

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?

This is a complex create tool with 10 top-level parameters and a deeply nested routing-tree payload, and there is no output schema. The description explains the core flows concept but leaves most top-level parameters and many behavioral details undocumented, so it is not complete enough for the tool's complexity.

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 only 10%, so the description needs to compensate but only covers part of the flows payload format. It says nothing about top-level parameters such as tags, group_id, auto_metric, description, flow_rotation, auto_min_clicks, or auto_explore_percent, and even its flows summary omits many nested fields documented in the schema.

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 states a specific verb and resource: creating a reusable flow scheme, and it explains that this is a routing tree applicable to campaigns. It does not explicitly distinguish the tool from siblings such as update_flow_scheme or apply_flow_scheme, so it stops short of full sibling differentiation.

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 implies this tool is for creating a new reusable scheme, but it gives no explicit when-to-use guidance and does not mention when to choose update_flow_scheme or apply_flow_scheme instead. The agent must infer the intended usage from the verb alone.

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