get_element_info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool can 'get the value of the element', which hints at read-only behavior, but doesn't cover critical aspects like error handling (e.g., if element not found), performance implications, or authentication needs for the session.

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, efficient sentence that front-loads the core purpose. However, it could be more structured by separating query methods from value retrieval, and the phrase 'can get the value of the element' feels tacked on rather than integrated.

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 3 parameters with 0% schema coverage and no annotations, but with an output schema present, the description is moderately complete. It covers the basic purpose and query methods but lacks details on parameter usage, error cases, and behavioral context, which are needed for a tool interacting with DOM elements.

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%, so the description must compensate. It mentions 'index or xpath query', which partially explains two parameters, but doesn't clarify the 'session_id' parameter or provide details on query syntax, default behaviors, or mutual exclusivity between index and xpath.

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 verb ('Get') and resource ('detailed information about a DOM element'), specifying it supports index or xpath query. It distinguishes from siblings like 'get_page_state' or 'get_instance_info' by focusing on element-level details, though it doesn't explicitly name alternatives.

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 alternatives is provided. It mentions supporting index or xpath query but doesn't specify prerequisites (e.g., needing an active browser session) or compare to siblings like 'get_dropdown_options' for specific element types.

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