create_flowchart

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

With no annotations, the description carries the behavioral burden and does a solid job: it discloses the auto-layout algorithm, hand-drawn Excalidraw style, graph complexity handling, CJK text support, default output path, and returned absolute path. It does not mention overwrite behavior or failure modes, but the disclosed traits go well beyond a generic 'creates a flowchart'.

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 compact and front-loaded: the first sentence states exactly what it does, followed by useful capability notes, a tidy Args block, and a Returns line. No wasted sentences or redundant restatements.

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, 2-required-parameter tool with no annotations, the description plus schema covers required inputs, defaults, output format, and behavioral capabilities. A brief note about overwriting existing files or a tiny example would make it fully complete, but nothing essential for invoking it correctly is missing.

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?

Since the top-level schema has no parameter descriptions, the Args section meaningfully compensates by explaining all six parameters and their defaults (direction values, output_path default, theme default). It omits some nested options like edge style/bidirectional and node shape/group, though those are covered in the schema's $defs.

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 names a specific verb and resource ('Create a flowchart diagram') and adds distinguishing specifics: Sugiyama hierarchical auto-layout, hand-drawn Excalidraw output, and support for branches, merges, cycles, and disconnected subgraphs. This makes it easy to tell apart from sibling diagram tools even without opening the schema.

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 the tool is for creating flowcharts programmatically from nodes and edges, but it never states when to prefer this over siblings such as import_mermaid_flowchart or create_diagram. There is no explicit when-not guidance or mention of alternatives.

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