visualize_ocdfg

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

No annotations provided, so description carries full burden. Discloses output format (PNG, SVG), coloring by object type, and default frequency annotations. Adds useful behavioral traits beyond the schema.

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?

Two concise sentences covering purpose and key features without redundancy. Front-loaded verb 'Render' and efficient use of parentheses for format.

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?

Covers core functionality and output traits for a visualization tool. Lacks details on output delivery (URL vs base64) but is sufficient given the single parameter and lack of customization options.

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?

Only one parameter 'ocdfg_id' with 0% schema documentation. Description does not explicitly define it, but tool context and name imply it is an identifier from discover_ocdfg. Adequate for a single required parameter.

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?

Description clearly states it renders an OC-DFG as PNG+SVG, specifying the source from 'discover_ocdfg'. This distinctly separates it from sibling visualization tools like 'visualize_dfg' or 'visualize_petri_net'.

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?

Implies usage after discovering an OC-DFG, but no explicit guidance on when to use vs alternatives. Lacks conditions or exclusions.

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