get_dom_node

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

With no annotations, the description carries the behavioral disclosure burden. 'Inspect' and the property list imply a non-mutating read operation. However, it does not disclose behavior for missing nodes, selector/nodeId precedence, or time out-of-range conditions, though these are not critical for a read-only inspection.

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?

A single sentence with no filler; the action, target, temporal scope, and property list are all front-loaded and useful.

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 description is adequate for a simple inspection tool, but with no annotations and no output schema, it leaves behavior under-specified (e.g., how nodeId and selector interact, missing-node handling, and any distinction from the many sibling DOM inspection tools).

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%, so the schema already explains all four parameters. The description adds which properties will be inspected, enriching the expected result, but does not add new meaning about nodeId vs selector or timestamp semantics beyond the 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 identifies the operation as inspecting detailed properties of a specific DOM node at a timestamp, and lists the property categories. It distinguishes itself through 'specific' and 'at a given timestamp' from live/snapshot siblings, but does not explicitly name an alternative tool.

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?

There is no guidance on when to choose this tool over the many siblings (e.g., get_dom_subtree, inspect_live_element, get_live_dom_snapshot). The 'given timestamp' implies historical inspection, but no when-to-use or when-not-to-use conditions are stated.

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