dom_get_value

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

With no annotations, the description carries the behavioral disclosure burden. The verb 'Get' and the word 'current' communicate a read operation on a live DOM value, but the description does not mention return format, behavior when the element is missing, whether it waits for the element, or any error semantics.

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 sentence with no filler, front-loading the action and object clearly. Every word earns its place and nothing extraneous is included.

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?

The tool is simple, its two parameters are fully documented, and the core purpose is stated. However, without an output schema or annotations, the description could be more complete by noting what the tool returns and what happens when the selector does not match an input element.

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%: both selector and targetId are documented in the input schema. The description adds no parameter-level detail, but the schema already provides the necessary semantics, so this is an acceptable 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?

The description clearly names the action ('Get') and the resource ('input element value'), so an agent can tell what the tool does. However, it does not explicitly distinguish itself from sibling tools like dom_input_value or dom_query, so it lacks sibling differentiation.

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 is given for when to use this tool versus alternatives. The description does not mention dom_input_value, dom_query, or any conditions, exclusions, or prerequisites, leaving the agent to infer usage entirely from the name and short description.

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