zen_snapshot

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

With no annotations, the description carries full burden. It discloses the action (snapshot), element scope, and filtering, but omits details about the output format (e.g., JSON/HTML), whether it modifies the DOM, and performance considerations. Adequate but not comprehensive.

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 two sentences, front-loaded with the core action, and contains no superfluous words. Every sentence adds value.

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 tool has no output schema, and the description does not clarify the format of the 'structured snapshot' (e.g., JSON, HTML). For a data-returning tool, this lack of specification may lead to agent confusion. Adequate for simple usage but incomplete.

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 documents both parameters. The description repeats the filter enum and adds no new meaning for 'selector' beyond the schema's 'CSS selector to scope snapshot.' No additional semantic value.

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 'Get a structured snapshot of visible page elements with CSS selectors,' specifying the verb, resource, and filtering options. This distinguishes it from sibling tools like zen_screenshot (visual) and zen_get_page_text (text extraction).

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 mentions filtering with 'all,' 'interactive,' or 'form,' but does not explicitly explain when to use this tool versus alternatives such as zen_get_page_text or zen_screenshot. Usage context is implied but not fully spelled out.

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