Vizdown-MCP

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 states what the tool does (detection without rendering) and describes the return format, but doesn't mention error conditions, performance characteristics, or whether both parameters can be used simultaneously. It provides basic behavioral context but lacks depth for a tool with two parameters.

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 concise: a clear purpose statement followed by separate Args and Returns sections. Every sentence earns its place, with no redundant information. The three-part structure (purpose, parameters, returns) is efficient and well-organized.

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 has an output schema (implied by 'Returns' section), the description doesn't need to fully document return values. However, with no annotations and 0% schema description coverage for inputs, the description should do more to explain parameter usage and constraints. It provides adequate context for a detection tool but could better address the two alternative input parameters.

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 schema provides no parameter documentation. The description mentions both parameters in the Args section but only provides their names without explaining their purpose, relationship, or constraints. While it acknowledges the parameters exist, it doesn't add meaningful semantic information beyond what's already visible in the schema structure.

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 specific action ('List all detected diagram blocks') and resource ('diagram blocks'), distinguishing it from sibling tools like 'render_all_diagrams' and 'render_diagram' by specifying 'without rendering them'. This provides immediate differentiation and clarity about what the tool does versus its alternatives.

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 usage context by stating 'List all detected diagram blocks without rendering them', which suggests this tool is for detection/analysis rather than visualization. However, it doesn't explicitly state when to use this versus the rendering siblings or provide exclusion criteria. The context is clear but lacks explicit alternatives guidance.

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