nex_browser_snapshot

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

readOnlyHint already covers the safety profile, yet the description adds two genuinely useful behavioral facts beyond the annotations: the refs are ephemeral ('short-lived') and CAPTCHAs must be handled through the captcha toolchain rather than CDP/Python/image matching. It still omits what happens when a ref goes stale or how large a snapshot can be.

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 short sentences with the core action front-loaded and no filler. The second sentence is a policy note that is relevant but sits somewhat apart from the purpose statement, keeping it from being maximally tight.

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?

With no output schema and no annotations beyond readOnlyHint, the description should carry more weight on what a snapshot returns and how the refs are consumed by action tools; 'short-lived actionable refs' gestures at this but leaves the return shape and ref lifecycle unexplained.

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 only 60% (pageId, sessionId, target documented; boxes and depth undocumented), and the description contributes no parameter meaning at all — no mention of depth limiting, boxes overlay, or that target accepts either an e12-style ref or a CSS selector.

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?

States a specific verb and resource ('Capture an accessibility/ARIA snapshot') and adds the distinguishing output trait — 'short-lived actionable refs' — which separates it from siblings like nex_browser_get_text or nex_browser_take_screenshot that also read the page but return different artifacts.

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?

It gives one explicit routing rule ('Page CAPTCHA: start with nex_browser_captcha_prepare') and a prohibition, but never says when to prefer a snapshot over get_text, page_title, or take_screenshot, nor that it is the prerequisite for ref-based click/type/fill. Usage is implied rather than spelled out.

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