take_snapshot

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

The description discloses key behaviors beyond annotations: output caps at maxLines, scoping via selector, and full tree dump with saveTo. The readOnlyHint annotation is consistent. The description adds valuable behavioral context without contradictions.

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 highly concise: two sentences that front-load the purpose and cover the essential usage constraints. Every sentence is informative with no wasted words.

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?

Given 8 parameters and no output schema, the description covers core behavior (maxLines, selector, saveTo) but does not detail return format or interactions with all params (e.g., maxDepth, preview). However, param descriptions fill most gaps, making it adequately complete.

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%, setting a baseline of 3. The description adds value by explaining interactions (saveTo overrides maxLines, selector scoping) and default behavior, which goes beyond individual parameter descriptions.

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 captures a DOM snapshot with stable UIDs. It uses specific verbs and resource ('Capture DOM snapshot'), and distinguishes from sibling tools like screenshots (visual) and evaluate_script (scripts) by focusing on DOM structure with UIDs.

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 advises to 'Retake after navigation', providing clear context for when to use the tool. However, it does not specify when not to use it or list alternatives, slightly missing the highest clarity standard.

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