visualize_oc_petri_net

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

Discloses output as PNG and SVG, but no annotations provided, and does not confirm read-only nature or describe side effects beyond rendering.

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, direct sentence with no unnecessary words, immediately communicates the tool's core function.

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?

Adequate for a simple rendering tool, but missing description of return format (e.g., inline vs. link) and could mention that both PNG and SVG are included.

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 ocpn_id is not described in schema; description hints it comes from discover_oc_petri_net but does not explain format or how to obtain it.

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?

Clear verb 'Render', specific resource 'object-centric Petri net', and distinguishes from siblings like visualize_petri_net by mentioning the source discover_oc_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 discover_oc_petri_net but lacks explicit when-to-use vs. alternatives like visualize_petri_net or visualize_dfg.

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