act

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

With no annotations, the description carries full burden. It mentions that for action='read' the text is returned in 'content' and that backend is selected based on element_id prefix, but fails to disclose side effects, synchronization, or error behavior for mutating actions.

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 concise, listing actions and parameters without unnecessary text. It front-loads the purpose and is well-organized, though a bit terse.

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?

No output schema exists, so description should address returns. It does for read, but not for other actions. Missing details on prerequisites (element from capture/find) and error handling. Adequate but not thorough.

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 explains 'text' for type, 'value' for set_value, and 'content' for read, but does not elaborate on 'element_id' or 'action' beyond listing options. Partial improvement over bare schema.

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 performs an action on an element from capture()/find(), listing specific actions. This distinguishes it from sibling tools like capture/find (element retrieval) and browser_goto (navigation).

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 details the available actions and their parameters, but does not explicitly state when to use this tool versus alternatives or provide exclusions. The context is implied but not formal.

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