element_get_options

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

With no annotations, the description adds value by disclosing the return data structure (text, value, index, selected status). It implies a read-only operation without side effects, though it doesn't explicitly state safety or potential errors.

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 three short sentences, each serving a clear purpose: function definition, usage context, and required inputs. No redundant information.

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 no annotations and low schema coverage, the description provides essential context but omits explanation of two parameters ('by', 'tab_id') and potential error cases. The existence of an output schema reduces the need to describe return format, but parameter gaps remain.

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 coverage is 0%, so the description must compensate. It only mentions 'locator' and 'element_id' as identifiers, failing to explain 'by' and 'tab_id'. This leaves ambiguity about when to use these other parameters.

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 retrieves options of a <select> element, specifying the data returned (text, value, index, selected status). It distinguishes from the sibling 'element_select' by indicating this tool is used before selection.

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 explicitly states when to use the tool ('before element_select') and hints at required inputs ('Provide locator or element_id'). It lacks explicit when-not-to-use or alternative tools beyond element_select.

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