ie_select

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

No annotations provided. Description only states how to identify the option but does not disclose what happens after selection, error conditions, or side effects. It implies mutation of the dropdown selection but is not explicit.

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?

Single sentence of 15 words, no fluff. All information is front-loaded and to the point.

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 tool with 6 parameters and no output schema or annotations, the description is too sparse. It does not explain the return behavior, failure cases, or the role of all parameters. Additional context is needed for effective use.

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 50% coverage with descriptions for index, label, and option_value. The description adds context that these are the selection methods, but it fails to explain the 'by' and 'value' parameters which are in the schema. The description partially compensates but introduces ambiguity.

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 selecting an option in a select dropdown via label, option_value, or index. However, the requirement to provide exactly one conflicts with the schema having two required parameters (by and value), causing slight confusion.

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 compared to sibling tools like ie_click or ie_fill. The description says to provide exactly one of the identifiers, but the schema requires both 'by' and 'value', which is contradictory.

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