generate_flow_diagram

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

Annotations already declare readOnlyHint=true, indicating this is a safe read operation. The description adds minimal behavioral context beyond this—it doesn't mention output format (e.g., image file, URL), performance characteristics, or any side effects. However, it doesn't contradict the annotations, and the example in the schema description provides some practical guidance on data structure.

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, efficient sentence that front-loads the core purpose. The second clause ('such as, scenarios requiring linear process presentation') adds useful context without redundancy. However, it could be slightly more structured by explicitly mentioning the input data format or output type.

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 tool's moderate complexity (5 parameters, nested objects) and rich schema coverage, the description is adequate but minimal. It lacks details on output (no output schema provided), doesn't explain how the flow diagram is rendered or delivered, and misses sibling differentiation. With annotations covering safety, it's complete enough for basic use but leaves gaps for advanced scenarios.

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 fully documents all parameters. The description doesn't add any parameter-specific semantics beyond what's in the schema—it doesn't explain the 'data' structure's purpose or how 'nodes' and 'edges' relate to flow diagrams. With high schema coverage, the baseline is 3, and the description doesn't enhance this.

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's purpose: 'Generate a flow diagram chart to show the steps and decision points of a process or system.' It specifies the verb ('generate'), resource ('flow diagram chart'), and target ('process or system'). However, it doesn't explicitly differentiate from sibling tools like 'generate_network_graph' or 'generate_mind_map' which might also visualize processes.

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 provides some implied usage context with 'scenarios requiring linear process presentation,' suggesting this tool is for linear workflows. However, it doesn't explicitly state when to use this versus alternatives like 'generate_sankey_chart' for flows or 'generate_organization_chart' for hierarchical processes. No explicit exclusions or prerequisites are mentioned.

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