get_node

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

No annotations are provided, so the description carries full burden. It discloses that it returns specific node data and requires a prior snapshot, but it does not mention error behavior (e.g., invalid uid) or explicitly state that it has no side effects.

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?

One sentence that front-loads the action and outputs, with no filler. Every clause adds value, and the prerequisite is clearly stated.

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?

Simple tool with one parameter and no output schema. Description covers purpose, exact return items, and prerequisite. It lacks error/no-result behavior, but given the simplicity, this is adequate and fits well within the snapshot workflow indicated by 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?

Input schema has 100% coverage with 'Stable uid from the snapshot output.' The tool description reinforces this by saying 'one snapshot uid' and 'Requires prior smart_snapshot or snapshot_diff,' but adds no new syntax or format details. Baseline 3 for full schema coverage.

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 uses the specific verb 'Return' and enumerates exact outputs (role, path, DOM geometry, CSS selector) for a single snapshot uid. This clearly distinguishes it from siblings like smart_snapshot or snapshot_diff which create snapshots/diffs.

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 explicitly states a prerequisite: 'Requires a prior smart_snapshot or snapshot_diff.' This gives clear context for when the tool can be used, but it does not mention alternatives or exclusion cases.

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