visualize_bpmn

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

No annotations provided; description states output formats but does not disclose other behavioral traits like side effects or permissions. As a rendering tool, it is likely safe, but lacks explicit statements.

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?

Single sentence front-loads purpose with no wasted words; highly concise.

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 one-param tool without output schema, description adequately states purpose and output format, but could mention that output is images and clarify the ID source more explicitly.

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?

Single parameter 'bpmn_id' has no description in schema (0% coverage). Description hints it comes from discover_bpmn but does not explain format or how to obtain the ID.

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 verb 'Render', the resource 'BPMN diagram', specifies it comes from 'discover_bpmn', and lists output formats 'PNG + SVG', distinguishing it from sibling visualization tools.

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 implicitly indicates usage after discover_bpmn but lacks explicit guidance on when not to use it or alternatives among other visualization tools.

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