session_snapshot

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It communicates that this is a capture operation and names the output categories, but it does not explicitly state whether the page is modified, whether authentication is needed, or whether the snapshot is purely read-only.

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 a single, front-loaded sentence with no filler. It efficiently conveys the core purpose and the main output categories without wasting tokens.

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, the description should explain the refs structure, what 'active element' means, and what happens when tabId is omitted. None of these are addressed, and the tool's relationship to sibling read/capture tools is unclear, making the overall definition 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 0%, and the description does not mention the optional tabId parameter or explain what happens when it is omitted. The parameter name gives a minimal hint, but the semantics of targeting a tab and the default behavior are left entirely undocumented.

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 states a specific action ('Capture a semantic snapshot') on a specific resource ('a page') and enumerates the captured contents: URL, title, active element, and interactive elements with refs. It does not explicitly distinguish this from sibling tools like session_read_page or session_screenshot, so it falls just short of a 5.

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?

There is no guidance on when to use this tool versus session_read_page, session_evaluate, or session_screenshot. The description never mentions prerequisites, typical invocation timing, or exclusions, so the agent must infer appropriate usage from context.

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