Get Property

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the context of 'live' (reading current state) and an example, but does not provide deeper behavioral details such as error handling, timing, or interaction with shadow DOM/frames beyond what annotations imply.

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, focused sentence that directly states the tool's purpose. It is front-loaded with the action and resource, contains no extraneous words, and every word earns its place.

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 a simple getter with rich annotations and a fully described parameter schema. The output schema exists, so return values need not be described. The description is sufficient for basic use, but slight gaps remain regarding when to prefer this over similar siblings.

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?

The input schema provides 100% coverage with descriptions for both parameters: 'property' and 'selector' (including selector syntax details). The description does not add additional parameter semantics beyond the schema, so the baseline 3 applies.

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 a specific verb ('Get') and resource ('live DOM property value from an element'), with a concrete example ('such as an input's current value'). It distinguishes itself from sibling tools like element_get_attribute by using 'property' rather than 'attribute', and from element_get_text/element_get_html by specifying 'DOM property value'.

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 implies usage for reading live properties, but it does not explicitly state when to use this tool versus alternatives like element_get_attribute or element_get_text. There is no mention of exclusions or alternative tool names, so guidance is only implied, not explicit.

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