Vizdown-MCP

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it parses the entire document, finds every diagram block, renders each separately, optionally saves output files with specific naming conventions, and returns a list of result dicts. It doesn't mention performance implications, error handling, or file system permissions, but provides substantial operational context.

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 and appropriately sized: a clear purpose statement, followed by detailed behavioral context, then organized parameter documentation, and finally return value information. Every sentence earns its place with zero waste, and the information is front-loaded with the core functionality stated first.

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?

Given the tool's complexity (7 parameters, batch processing), no annotations, and the presence of an output schema, the description is remarkably complete. It covers purpose, behavior, detailed parameter semantics, and return structure. The output schema handles return values, so the description appropriately focuses on operational context and parameter guidance.

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?

With 0% schema description coverage for 7 parameters, the description compensates excellently by providing detailed parameter semantics in the Args section. It explains each parameter's purpose, acceptable values (e.g., output_format options, theme options), defaults, and even file naming conventions for output_dir. This adds substantial meaning 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 tool's purpose: 'Render ALL diagram blocks found in a Markdown file' with specific details about parsing the entire document, finding every diagram block, and rendering each separately. It distinguishes from sibling tools 'list_diagrams' and 'render_diagram' by emphasizing processing ALL diagrams rather than listing or rendering individual ones.

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 provides clear context about when to use this tool: for processing all diagrams in a Markdown file. It doesn't explicitly state when NOT to use it or name alternatives, but the context implies this is for batch processing versus the sibling 'render_diagram' for single diagrams. The guidance is clear but lacks explicit exclusions or named alternatives.

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