Page Snapshot

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

No annotations provided, so description must carry behavioral info. Mentions 're-snapshot' implying refresh, but does not describe side effects, whether previous snapshot is cleared, or performance implications. Adequate but minimal.

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?

Two sentences: first states purpose, second gives usage guidance and a tip. Efficient and front-loaded 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?

Covers main purpose, when to use, and key parameter advice. Missing explicit description of what the snapshot returns (no output schema), but typical behavior is implied (refreshes internal state). Reasonably complete for a three-parameter tool.

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 coverage is 100%, so baseline is 3. Description adds value by explaining that 'selector' scopes the snapshot and reduces tokens, which goes beyond the schema's 'CSS selector' label.

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?

Clearly states 'Re-snapshot the current page for fresh @eN refs', which is a specific verb and resource. Differentiates from sibling tools like 'act' and 'navigate' by focusing on refreshing the snapshot state.

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?

Explicitly advises use after 'act' when re-orienting is needed and recommends 'selector' to reduce tokens. Provides concrete examples ('form', '#results'). Lacks explicit when-not-to-use but context is clear.

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