chrome_select

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

No annotations exist, and the description only states what the tool does without disclosing behavioral traits such as waiting behavior, error handling, or what happens on element not found. The `waitMs` parameter is not explained, and there is no mention of side effects or permissions.

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 sentence that immediately states the action and method. It is concise with no redundancy, and every word adds value.

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 8 parameters and no output schema or annotations, the description leaves many details uncovered. It does not explain the return value, error behavior, or how parameters like tabId or urlContains affect execution. The description is insufficient for complete agent understanding.

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 description adds meaning to three parameters (selector, label, value) by explaining that the selector or label identifies the dropdown and value matches option text or value. However, five parameters (tabId, waitMs, debugUrl, urlContains, titleContains) are unaddressed, and with 0% schema description coverage, the description only partially compensates.

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 action ('Set a select dropdown') and the method ('by CSS selector or label text, matching option value or visible text'), distinguishing it from sibling tools like chrome_click or chrome_type which handle different UI interactions.

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 explicit guidance on when to use this tool versus alternatives. The purpose is clear, but there is no mention of prerequisites, limitations, or when not to use it, which leaves some ambiguity for the agent.

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