get_dropdown_options

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

No annotations are provided, so the description carries the full behavioral burden. 'Get all options' implies a read, but there is no statement of side effects, whether the element must be visible/expanded, or what happens on an invalid index. For a zero-annotation tool this is thin.

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?

One compact sentence after the shared browser-context prefix, with the action front-loaded. The prefix is boilerplate but justified for routing decisions among browser-vs-other tools.

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 no annotations and no output schema, the description should at least hint at the return shape (a list of option labels/values) and indexing semantics, neither of which appears. It is minimally adequate for a simple read tool but leaves real gaps.

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 100% ('index of the dropdown element', 'Purpose of this action'), so the schema already documents both parameters. The description adds no syntax, indexing base, or format detail beyond that, making 3 the correct baseline.

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?

States a specific verb (get all options) and resource (native dropdown), which clearly separates it from the write-side sibling select_dropdown_option. It stops short of naming that sibling, so differentiation is implied by verb rather than explicit.

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 bracketed note 'use only when the task requires acting on a real website' gives a when-to-use condition, but it is generic boilerplate shared across this whole tool family rather than guidance specific to dropdown inspection. Nothing says whether the dropdown must be opened first or how it relates to select_dropdown_option.

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