cdp_select

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

No annotations are provided, so the description must cover behavioral traits. It adds the selection mechanism ('by value, label, or index') but omits important side effects such as whether it triggers change events, handles multi-select, waits for page updates, or errors when no matching option is found. This is not enough for an agent to predict runtime behavior.

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 leads with the verb and object, immediately stating the tool's purpose. It contains no redundant wording or filler, making it optimally scannable.

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?

With six parameters, no annotations, and no output schema, the description should provide more operational context. It does not mention return values, error conditions, prerequisites like an active session (beyond the session_id parameter), or the effect of selecting options on the page state. This leaves the agent under-informed for a tool with moderate complexity.

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 17%, so the description must compensate. It clarifies the roles of value, label, and index, but does not explain the 'selector' syntax (e.g., CSS selector) or the 'values' array for multiple selection. This leaves significant gaps for the agent to choose and set parameters correctly.

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's function with a specific verb ('Choose'), a targeted resource ('<select> element'), and the selection criteria (value, label, or index). This distinguishes it from sibling tools like cdp_click or cdp_type.

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 when to use the tool by mentioning '<select> element', but it does not explicitly contrast with alternatives or state exclusions. For example, it does not mention that cdp_evaluate could be used for more complex DOM manipulations or when to prefer cdp_click.

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