element_get_info

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

No annotations provided, so description carries full burden. It discloses output fields but does not explicitly state read-only nature, error behavior, or that it does not modify the page. Adequate for a simple get but could be more transparent.

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?

Two sentences with no extra words. Front-loaded with the main action and returned fields. Efficient and to the point.

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?

Has output schema so return values are covered. However, given 4 parameters and many siblings, missing details on when to use tab_id or how to combine parameters. Feels somewhat incomplete for a tool with multiple input options.

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 description must compensate. It advises 'Provide locator or element_id', but does not explain the 'by' or 'tab_id' parameters, leaving ambiguity. Partially helpful but incomplete.

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?

Description clearly states 'Get full element details' and lists specific fields (tag, text, rect, attrs, html, states). It differentiates from sibling element_find by noting it returns 'richer info', making the tool's purpose distinct.

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?

Explicitly says 'Provide locator or element_id', guiding input choice. Implicitly suggests usage when full details are needed vs. element_find, but lacks explicit 'when not to use' or prerequisites like required permissions.

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