robot_list_failover

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

Declares 'Read only, free' indicating safety and cost, and 'Compact by default' hinting at the verbose parameter. However, no mention of rate limits, permissions, or pagination behavior. Annotations are absent, so description partially compensates.

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?

Extremely concise with three short sentences. No redundant information. Front-loaded with the core action.

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 list tool with 3 parameters and no output schema, the description is minimal but covers the core purpose. Lacks detail on query parameter usage and failover IP specifics. Adequate but not rich.

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 coverage is 100% with parameters id, query, verbose. Description only adds context about compact vs verbose via 'Compact by default'. Does not elaborate on id or query beyond 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?

Description explicitly states 'List failover IPs', a specific verb and resource. Clearly distinguishes from sibling list tools like robot_list_servers or robot_list_ips.

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 on when to use this tool versus alternatives. Sibling list tools exist for different resources, but no comparison or prerequisites are provided.

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