list_turnouts

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

Discloses important behavioral detail about the 'has_feedback_sensor' field and how to interpret INCONSISTENT state, which is critical for correct agent reasoning, especially with no annotations provided.

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?

Every sentence is informative and essential, front-loaded with main purpose, followed by usage guidance and a nuanced behavioral note. No redundancy.

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?

Covers main output fields and their interpretation, though could explicitly list all return fields. Given no output schema, it does well to contextualize the response.

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?

No parameters exist, so baseline is 4. The description adds value by explaining output semantics, compensating for lack of output 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?

The description clearly states it lists all turnouts with their state, using specific verbs ('list', 'discover') and distinguishes from siblings like get_turnout and set_turnout.

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 (before get_turnout/set_turnout, to answer specific queries) and declares no side effects, guiding appropriate invocation.

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