set_valve_status

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

The description does not disclose side effects, prerequisites, or whether the operation is reversible. With no annotations provided, the description carries full responsibility for behavioral transparency but only states the action without any deeper context.

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 extremely concise, with a front-loaded purpose statement and a succinct parameter list, containing no unnecessary words.

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 the simplicity of the tool, the description lacks usage guidelines and behavioral transparency, leaving the agent without sufficient context to use it correctly, especially given the many sibling tools with similar names.

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 description adds brief explanations for each parameter (e.g., network_id as session id, valve_id as link name/ID, status values as 'OPEN' or 'CLOSED'), but with 0% schema coverage, it does not fully compensate by providing additional meaning or constraints.

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 'Open or close a valve' using a specific verb and resource, effectively distinguishing it from sibling tools like set_valve_setting and set_pipe_status.

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 to use this tool versus alternatives such as set_valve_setting, nor are prerequisites or context for usage mentioned.

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