browser_select_dropdown_by_text

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

With no annotations, the description carries full behavioral disclosure burden. It does not mention if it deselects previous options, waits for the element, or requires a <select> element. The input schema includes a timeout parameter, but the description omits any behavioral details.

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 only 5 words, which is concise but too minimal. It lacks details such as that the dropdown element must first be located using 'by' and 'value' parameters, and then the option is selected. While not verbose, it misses necessary context.

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 tool with 4 parameters and no annotations or output schema, the description is insufficient. It does not explain the overall workflow (locate element then select option), the supported element types (e.g., <select>), or potential side effects. This leaves gaps for correct agent invocation.

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?

Input schema coverage is 100% (all parameters have descriptions). The description adds no additional meaning beyond the schema, so it scores the baseline of 3. The description lists the 'text' parameter but doesn't clarify matching behavior (exact match, case sensitivity, etc.).

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 'Select dropdown by visible text' clearly states the action (select) and resource (dropdown) and distinguishes from sibling 'browser_select_dropdown_by_value' by specifying the selection criterion (visible text). However, it could be more explicit about the element type and selection mechanism.

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 guidance on when to use this tool versus the sibling 'browser_select_dropdown_by_value' or other dropdown-related tools (e.g., browser_click followed by option selection). This leaves 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.