select

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose side effects, whether selection triggers change events, what prerequisites exist for the ref, or what happens after selection, beyond the optional snapshot parameter in the schema.

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?

A single efficient sentence, front-loaded with the verb and target element. Every phrase adds necessary meaning without waste.

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 browser automation action with no annotations and no output schema, the description omits important context such as where ref comes from, what occurs after selection, and how multi-select is handled. Siblings like snapshot and click imply a richer context that the description does not address.

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 description coverage is only 33%, with just the snapshot parameter documented in the schema. The description clarifies that values match option value or label and that multiple options are possible, but ref is left unexplained beyond its name, so it only partially compensates for the low schema coverage.

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?

States a specific verb ('Choose') and resource ('option(s) in a <select> element'), plus the matching mechanism ('by ref, matching option value or label'). An agent can distinguish this from siblings like click, type, or evaluate without opening the schema.

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?

Provides no explicit when-to-use guidance, prerequisites, or conditions for choosing this tool over alternatives such as click, type, or evaluate. Usage is only implied by the mention of a select element.

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