pilot_select_option

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

No annotations are provided, so the description carries full burden. It describes the selection action, returns confirmation, and lists errors. However, it does not disclose whether change events are triggered or if there are side effects, which would be beneficial for a complete behavioral picture.

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 and well-structured: purpose, usage, parameter details, return value, and errors. Every sentence contributes meaning without unnecessary wordiness.

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?

The description is complete for a simple tool with two parameters. It covers return confirmation and two common error conditions, which compensates for the lack of an output schema.

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 input schema covers all parameters with descriptions. The description adds extra context: 'Select element ref (@e3) or CSS selector' and 'Option value, label, or text to select', providing more detail than the schema alone. Given 100% schema coverage, the description adds marginal value.

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 the tool selects an option from a <select> dropdown by value, label, or visible text. It distinguishes from clicking by noting that clicking an <option> in pilot_snapshot is auto-routed here.

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?

The description provides clear usage context: 'Use when the user wants to choose a dropdown option, select from a combobox, or pick from a list.' It also mentions auto-routing from pilot_snapshot. However, it does not explicitly state when not to use this tool versus alternatives like pilot_click.

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