set_simulation_duration

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

With no annotations, the description should disclose behavioral traits but only states the action without side effects, ordering constraints, or impact on other settings. It omits whether setting duration before running simulation is required or if it can be changed mid-simulation.

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 with two sentences, front-loading the purpose. However, it sacrifices completeness for brevity, missing contextual information.

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?

Despite having an output schema, the description lacks context about the tool's role in the simulation lifecycle, prerequisites, or behavioral implications. It feels incomplete for a tool that modifies simulation state.

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%, so the description bears the full burden. It adds meaning: network_id as 'Session id' and duration_s as 'Duration in seconds (e.g. 86400 = 24 h)'. This provides unit and example but lacks clarity on what constitutes a valid session id.

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 states it sets the total simulation duration, which is clear but essentially restates the function name without adding meaningful differentiation from siblings like 'set_hydraulic_timestep' or 'set_quality_timestep'. It is minimal and not distinguishing.

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 guidance is provided on when or when not to use this tool. It does not mention prerequisites (e.g., must have a loaded network) or compare with alternatives like 'run_simulation' that implicitly determine duration.

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