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

No annotations are provided, so the description must carry the full behavioral burden. It implies a read-only snapshot but does not disclose side effects, permission requirements, ref lifetime, or what the snapshot actually returns.

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 five-word phrase is concise and front-loaded, but it is under-specified rather than effectively structured. There is no wasted text, yet the brevity leaves key information missing.

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 annotations and no output schema, the description needs to explain what the snapshot contains and how refs are used. It does not do so, and it also leaves the interactive_only parameter unexplained, making the definition incomplete for a browser snapshot 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?

The schema covers tab_id and notification_message, but interactive_only has no description at all. The tool description does not explain any parameter, and 'with refs' provides no mapping to the inputs.

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 it returns an accessibility snapshot with refs, which is somewhat more specific than the tool name alone. However, it does not define what 'refs' are or clearly distinguish the tool from siblings such as browser_screenshot or browser_dom_input.

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 alternatives such as browser_screenshot, browser_interact, or browser_actions. The agent must infer usage entirely from the name and the vague phrase 'accessibility snapshot with refs.'

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