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

Annotations already declare non-readonly, open-world, non-idempotent behavior, so the bar is lower. The description still adds real context beyond them: the 1 AI credit cost, the Pro-tier requirement for advanced types, and what the output actually is (editable board, animated presentation, PNG/PDF/PowerPoint export, Mermaid for some types). It omits failure modes and rate limits, so not a 5.

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?

Front-loaded with the core action and outcome, then a dense type catalogue. The long enum list earns its place because it disambiguates 15 values, though the sentence is heavily parenthesized and could be tighter.

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?

No output schema exists, so the description correctly explains the return artifact (link/board/Mermaid) and the cost model. Annotations cover the safety profile. Minor gaps remain around input length limits or error behavior, but nothing an agent needs to invoke 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?

Schema coverage is 100%, so baseline is 3, but the description goes beyond the raw enum by explaining what each type means (e.g. 'sequence (API / login flows)', 'erdiagram (database)', 'bpmn (BPMN 2.0 business process)'). It also reinforces the description parameter's intent to include names and specifics.

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?

States a specific verb and resource ('Create a diagram in AI Flowchart from a plain-English description') plus the concrete payoff ('a link that opens it as an editable board'). The 'plain-English description' framing implicitly separates it from code_to_flowchart, which takes code as input.

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 when this tool applies (you have a textual description of a process/system/data) and enumerates the supported diagram types, which aids selection. However, it never explicitly says when to prefer this over code_to_flowchart or the template tools, nor states any exclusions.

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