visualize_net_tool

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool visualizes and saves a PNG, but fails to mention whether it is read-only, modifies any files, requires network connectivity, or has side effects like creating directories. The destructive hint and read-only hint are absent, leaving the agent unsure of safety.

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 concise (6 lines) with a clear hierarchy: single-sentence purpose, usage warning, and parameter list. Every sentence adds value, and the warning is front-loaded for quick agent comprehension.

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 no output schema and 0% schema coverage, the description should provide more context about the tool's output (e.g., file path or success message) and error handling. While it covers usage and parameters, it omits result details, making it incomplete for an agent to understand the full tool behavior.

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?

The schema has 0% description coverage (only titles), so the description's Args section adds crucial meaning: it clarifies that net_file expects a '.net.xml' path and output_dir is the directory for visualization files. This fills a significant gap, though it doesn't explain the default behavior of output_dir.

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 action ('Visualize a SUMO network file and save as PNG image'), specifying the resource as a SUMO network file. While it doesn't explicitly differentiate from sibling visualization tools like visualize_edge_tool, the tool name ('net_tool') and the focus on 'network file' provide adequate distinction.

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 provides explicit, actionable guidance: 'Only use when user EXPLICITLY requests visualization!' with concrete examples of when to use ('show network map', 'visualize network') and when not to use ('questions about simulation results'). This is exemplary for guiding an AI agent.

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