Select option

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

Annotations already declare readOnlyHint=false and destructiveHint=true, indicating mutation and destructiveness. The description adds no further behavioral context (e.g., whether prior selections are cleared, error conditions, or side effects). The agent gains no additional insight beyond what structured annotations already provide.

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?

While the description is short and front-loaded, it is too minimal to be useful. It does not earn its place because it omits critical information about parameters and usage; conciseness here sacrifices clarity for brevity.

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 (2 required), no output schema, and annotations that signal destructiveness, the description is grossly incomplete. It fails to explain how to target the dropdown, specify options, or interpret results, leaving the agent without sufficient context for correct 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?

Schema description coverage is 0% – no parameter descriptions exist in the input schema. The tool description ('Select an option in a dropdown') provides zero explanation of what 'target', 'values', or 'element' mean or how to use them. The description fails to compensate for the absent schema semantics, leaving the agent completely uninformed about parameter usage.

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 an option in a dropdown' uses a specific verb ('Select') and resource ('dropdown'), clearly distinguishing it from sibling tools like browser_click or browser_fill_form. It explicitly states the action and target element 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 provides no guidance on when to use this tool versus alternatives (e.g., browser_click, browser_fill_form), nor does it state any prerequisites or exclusions. The agent is left to infer usage context from the tool name alone.

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