browser_get_accessibility_snapshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'get accessibility snapshot' and does not reveal output format, whether the operation is read-only, or any side effects. This is insufficient for an agent to predict tool behavior.

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 extremely short and contains no wasted words, but this is under-specification rather than concise clarity. It offers zero explanatory content beyond the tool's name, so it fails as a useful description.

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?

For a tool with no annotations, no output schema, and a single undocumented parameter, the description is wholly inadequate. The agent cannot determine what an accessibility snapshot contains, how the selector influences the result, or what the return value looks like.

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 defines one optional 'selector' parameter with no description, and schema description coverage is 0%. The tool description does not mention the selector at all, so the agent is left guessing what the parameter does and how to use it.

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 '获取无障碍快照' is simply the Chinese translation of the tool name 'browser_get_accessibility_snapshot', restating the name without adding any explanatory value. It fails to clarify what an accessibility snapshot is, what it includes, or how it benefits the agent.

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 provides no guidance on when to use this tool versus any of the many sibling browser tools. There are no use cases, prerequisites, or exclusions mentioned, leaving the agent without decision-relevant information.

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