visualize_petri_net

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

No annotations provided, so description carries full burden. It only mentions output format (PNG+SVG) but lacks details on side effects, permissions, error handling, or return behavior. The behavioral disclosure is minimal.

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 with no wasted words. Front-loaded with action and resource. Every word earns its place.

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 simple one-parameter tool with no output schema, the description covers the core purpose. However, it lacks details on validation (e.g., what if petri_id is invalid) and how the PNG+SVG output is delivered. Somewhat adequate but not fully complete.

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 coverage is 0%, and the description adds little meaning beyond the parameter name. It references 'from discover_petri_net' which hints at the source of petri_id, but does not explain the format or how to obtain it. The description does not adequately compensate for the missing schema descriptions.

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 the tool renders a Petri net (from discover_petri_net) as PNG+SVG. The verb 'Render' and resource 'Petri net' are specific, and the source distinguishes it from other visualization siblings like visualize_dfg or visualize_bpmn.

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_petri_net, giving clear context. Does not explicitly state when not to use or list alternatives, but the source reference effectively differentiates it from other visualization tools.

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