flow

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

With no annotations, the description should disclose behavioral traits. It mentions loops/conditionals for 'run' and parallel execution, but omits key behaviors like timeout, error handling defaults, and sequential execution order. The schema covers some of this, but the description is insufficient for an agent to understand all behavioral nuances.

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 a single concise sentence that front-loads the purpose. It is not verbose, but could be slightly more structured (e.g., separating modes with bullet points) for clarity without losing conciseness.

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 complex orchestration tool with 8 parameters and three action modes, the description is too minimal. It does not explain when to use each mode, how steps differ from commands, or provide any workflow examples. The schema helps but is not a substitute for a comprehensive description.

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 88% (high), so baseline is 3. The description adds minimal meaning beyond the schema, only listing the three actions. No additional parameter details are provided, so it does not compensate for the 12% uncovered parameters.

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 tool is for 'flow orchestration' and lists three specific modes (batch, run, parallel) with brief explanations. This distinguishes it well from sibling tools (app, device, etc.), but the description lacks a clear verb-noun structure; 'orchestration' is a bit abstract.

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 usage via the three modes but does not explicitly state when to use this tool versus alternatives. No exclusion criteria or contextual guidance is provided, relying on the implicit differentiation from sibling tools.

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