save_network

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

No annotations provided. Description does not disclose error handling (e.g., invalid network_id, existing file), return value, or whether saving modifies the in-memory state. It only states the basic action.

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?

Description is concise with a main sentence and an Args list. Front-loaded with purpose. Minor improvement: could consolidate Args into table or bullet points, but no wasted prose.

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 save operation with 2 required params and no annotations, the description covers basic semantics but lacks return value description (output schema exists but not described), error cases, and behavior on existing files. Adequate but not comprehensive.

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 description coverage is 0%, but the description includes an Args section explaining each parameter: network_id as 'Session id of the network to save' and output_path as 'Destination file path (should end in .inp).' This adds meaning beyond the schema's type/title.

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 'Save the current (possibly modified) network to a new .inp file.' The verb 'save', resource 'network', and output format are specific. This distinguishes it from siblings like load_network and unload_network.

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?

No explicit guidance on when to use this tool vs alternatives. It implies saving after modifications but doesn't mention prerequisites, scenarios where other tools (like load_network) should be used first, or when not to use it.

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