create_flowchart

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

No annotations are provided, and the description only says 'create flowchart', disclosing no behavior about side effects, persistence, or return values. This leaves the agent entirely without safety or runtime context for a mutating operation.

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 phrase is extremely short, but this is under-specification rather than effective conciseness. The description merely mirrors the name and earns no place as added guidance.

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 creation tool with a nested steps array, no output schema, and no annotations, a one-phrase description is far too sparse to guide an agent. It lacks information about required fields, semantics of steps, layout options, or what happens after creation.

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?

The description contributes no parameter semantics; only 67% of params have schema descriptions, and layout is left without a textual explanation. The tool relies entirely on the schema, so the description fails to add value beyond structured fields.

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 '创建流程图' is a direct Chinese translation of the tool name 'create_flowchart', providing no additional specificity. It restates the name rather than explaining what creating a flowchart entails or how it differs from siblings like create_diagram or create_mindmap.

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?

No guidance is provided about when to choose this tool over create_diagram, create_timeline, or other siblings. The description offers no context or exclusions.

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