snapshot

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

With no annotations, description carries full burden. It implies a read operation by stating 'Return the current page state', but does not explicitly declare it non-destructive or mention side effects, timing, or permissions. Adequate but not thorough.

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?

Single sentence that efficiently outlines what the tool returns. Could be split for readability, but no wasted words. Appropriately front-loaded with verb and resource.

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?

Output schema exists, so return structure is covered. However, description lacks explanation of 'warnings' and 'next actions', and does not clarify how each parameter affects output. Mostly adequate given sibling tools but has gaps.

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 0%, so description must add meaning. Only implicitly covers include_screenshot via 'optional screenshot'. No mention of max_text_chars, include_dom, or include_iframes, leaving 3 of 4 parameters unexplained. Partially compensates but insufficient.

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?

Description clearly specifies verb 'return' and resource 'current page state', listing included elements (visible text, optional screenshot, warnings, next actions). It effectively distinguishes this read/capture tool from sibling action tools like click, fill, and select.

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?

No guidance on when to use this tool versus alternatives like click or fill. Does not mention that it should be used before actions for state capture or after actions for verification. Lacks context for typical usage scenarios.

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