textual_snapshot

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that the snapshot includes widget tree, refs, focus, bindings, and errors, which provides some behavioral context beyond annotations. However, it does not discuss performance, blocking, or output size. No contradiction with annotations.

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?

Single sentence, 22 words, front-loaded with key action and resource. No unnecessary words. Very concise.

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?

Tool has moderate complexity (3 params, 1 required, output schema exists). Description covers purpose but lacks parameter explanations critical for correct invocation. With 0% schema description coverage, this is a significant gap. Output schema exists but doesn't compensate for missing param info.

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 has 3 parameters (session_id, max_depth, include_styles) with 0% schema description coverage. The description does not explain any parameter meanings, such as that max_depth limits the widget tree depth or include_styles filters style information. Description adds no value for parameter understanding.

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 clearly states the verb 'Snapshot' and the resource 'current app state', and lists specific included elements (widget tree, refs, focus, bindings, errors). This distinguishes it from sibling tools like textual_screenshot (visual capture) or textual_query (search).

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?

No guidance on when to use this tool versus alternatives. Does not mention when it is appropriate to snapshot vs. using textual_check_errors or textual_query. No exclusions or prerequisites.

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