generate_diagram_from_ascii

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes what the tool does (converts ASCII art to visual diagrams), specifies acceptable input formats (box-drawing characters, arrow representations, plain text layouts), and explains the output behavior (returns a link to view and edit). It doesn't mention potential limitations like size constraints or error conditions, but covers the core behavior well.

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 perfectly structured with three sentences that each serve distinct purposes: stating the core function, specifying usage context, and explaining input/output behavior. There's no wasted language, and it's front-loaded with the most important information about what the tool does.

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 tool with no annotations and no output schema, the description provides good coverage of the tool's behavior, usage context, and input expectations. It explains what the tool returns (a link) which compensates for the missing output schema. The main gap is lack of information about potential constraints or error conditions, but overall it's quite complete for the tool's complexity.

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 already documents all parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it mentions 'box-drawing characters, arrow representations (-->, ==>), and plain text layouts' which aligns with the content parameter example, but doesn't provide additional context for other parameters. This meets the baseline expectation when schema coverage is complete.

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 with specific verbs ('convert', 'rendered') and resource ('ASCII art diagram'), and distinguishes it from siblings by specifying it's for ASCII art input rather than image, JSON, Mermaid, or text inputs. The phrase 'polished visual diagram' adds specificity beyond just conversion.

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 explicitly states when to use this tool ('when the user has an existing ASCII art representation') and implicitly distinguishes it from sibling tools by specifying ASCII art input. It provides clear context for usage without needing to name alternatives directly, as the sibling tool names make the differentiation obvious.

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