select

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention side effects (e.g., triggering change events), error behavior (e.g., option not found), or handling of multiple matches. It simply states the action without adding behavioral context.

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 extremely concise, with every word contributing to the purpose. It is front-loaded with 'Pick option(s) on a <select>' immediately. It avoids redundancy and is easy to scan.

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?

Given the tool's complexity (6 parameters, including optional lease and session), the one-line description is insufficient. It fails to explain precedence of selection criteria, behavior for multiple selects, error handling, or any edge cases. The schema covers parameter details, but the description adds no additional operational context.

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%, so each parameter is already described. The description adds the note that selection can be by value, label, or index, which is helpful, but it does not clarify precedence or interaction between these parameters. It adds minimal value 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?

The description clearly identifies the specific action (picking options) on a specific element (<select>), and distinguishes it from sibling tools like check/uncheck or click, which are for other element types. Mention of value/label/index makes the selection mechanism explicit.

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 gives no guidance on when to use this tool versus alternatives, nor does it explain prerequisites or exclusions. It merely states what it does, leaving the agent to infer that it's for select elements. No mention of when not to use it or how it differs from click or other tools.

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