processon_generate_chart

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

With no annotations, the description carries the full behavioral burden. It discloses the outcome ('Returns a preview image and an editable link'), the automatic layout behavior, and the model-decides behavior when chart_type is empty. It does not address side effects like account persistence or permissions, but for a diagram-generation tool the core behavior is well covered.

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 structure is front-loaded with the primary purpose, followed by supported types, output, usage trigger, and parameter explanations. There is minor redundancy between the first two sentences, and the 'Args' block is slightly verbose, but each section earns its place.

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?

The description is complete for invoking the tool: it explains both parameters, when to use the tool, what output to expect, and how to handle ambiguity. It relies on the output schema for return details, which is acceptable. The main gap is the lack of comparative guidance against sibling diagram-generation tools, which could affect tool selection in ambiguous cases.

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 0%, so the description must fully explain the parameters. It does: 'prompt' is detailed with content, language, and layout guidance, and 'chart_type' is explained with examples and the default behavior of leaving it empty. This adds substantial meaning far beyond the bare 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 clearly states the primary action ('Generate an editable online diagram') and the input ('natural-language description'), and enumerates many supported diagram types. It does not explicitly differentiate itself from siblings like processon_design_diagram or processon_render_mermaid, so it misses the sibling-distinguishing bar for a 5.

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 gives explicit 'Use this whenever...' guidance with concrete trigger phrases in both Chinese and English, and instructs the agent to ask when the chart type is ambiguous. It does not mention when not to use this tool or how to choose between it and potentially overlapping siblings.

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