Select page option

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

Annotations show readOnlyHint=false and destructiveHint=false, but the description adds that a missing or unsuitable select returns OPERATION_TIMEOUT within timeoutMs and that the session remains usable. This provides behavioral context beyond annotations, such as error behavior and session safety, which is valuable for an agent.

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 a single, concise sentence that includes key information: the action, the target, the locator types, and error behavior. It is front-loaded and every phrase adds value, with no redundancy.

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 tool is relatively complex with 6 parameters and a nested locator schema. The description covers the basic purpose and error behavior but lacks details on return values (though output schema exists), prerequisites for session/page existence, and specific examples of locator usage. With an output schema present, return values are covered, but the description still misses important context like how to construct locators or handle multiple selects.

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 schema has 6 parameters with 0% description coverage, so the description should compensate. While the description mentions using 'semantic or CSS locator' and 'timeoutMs', it does not explain specific parameters like sessionId, pageId, value, or the locator structure. The description adds minimal meaning beyond what the schema already defines, so it bears some responsibility for parameter clarity. Since schema coverage is 0%, the description should have done more, but it at least hints at the locator and timeout.

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 on a page using a semantic or CSS locator. It specifies the target resource (explicitly addressed page) and the action (selecting an option), which differentiates it from other browser interaction tools like click, fill, and check.

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 implies usage for selecting options from dropdowns but does not explicitly contrast with alternatives like click or check. It mentions 'explicitly addressed page' implying a prerequisite, but does not provide detailed when-to-use/when-not-to-use guidance relative to sibling tools.

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