set_all_turnouts

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

Discloses that it applies one state to all turnouts with no per-turnout memory, warns of motor movement on real layout, and explains catch-and-continue error handling. No annotations were provided, so description carries full burden and does so thoroughly.

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?

Well-structured with sections for Args, Call for, Blast radius, Returns. Every sentence adds value; no fluff. Efficiently conveys complex 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?

Comprehensive: covers purpose, usage, parameter, return format (succeeded/failed lists), error handling (catch-and-continue), and safety warnings. No output schema needed given the clear return description.

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 has no parameter description (0% coverage), but description fully explains the boolean 'thrown' parameter: true means THROW, false means CLOSE. Adds meaning beyond the schema.

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?

Clearly states it sets every turnout to the same state (all closed or all thrown) in one call, with specific verb and resource. Distinguishes from sibling set_turnout by saying 'Never loop set_turnout yourself'.

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?

Explicitly tells when to use (for layout-wide requests) and when not to (not as a shortcut for one turnout). Provides alternatives (use set_turnout for single turnout) and warns about blast radius.

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