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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the return is a text accessibility tree (a structural representation, not a screenshot), and it is scoped to desktop pages. It stops short of mentioning output size/pagination limits, so not a 5.

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 sentences, both load-bearing: the first defines what is returned and why, the second routes to the alternative. Scope and the sibling contrast are front-loaded with zero filler.

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 single-param, read-only snapshot tool with no output schema, the description covers purpose, output format, and the sibling boundary. Minor gap: no guidance on result size, truncation, or whether the tree covers the full page vs viewport, which would matter for a 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?

Only one parameter (pageId) and schema description coverage is 100%, with the schema itself linking to web_navigate ('Page ID from web_navigate'). The description repeats the 'by pageId' scope but adds no syntax or provenance beyond the schema, so the baseline 3 applies.

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+resource ('Accessibility tree of the DESKTOP grid browser page ... as text') and explicitly distinguishes itself from the mobile sibling by scope (desktop page vs device). An agent can differentiate it from webpage_snapshot and web_get_source without opening any schema.

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?

Gives the use case ('for finding elements and understanding layout') and an explicit exclusion with the correct alternative: phone/tablet work must go to webpage_snapshot (by udid). This is a clear when-to-use / when-not-to-use routing statement.

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