pbi_snapshot

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

No annotations provided, but description fully discloses behavior: read-only, returns indented lines of ARIA snapshot, selector scoping to sub-tree, filter regex with indent preservation, maxLines cap with default 400. Clearly labeled 'Read-only' at end.

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?

Three concise sentences: first states purpose and analogy, second describes output format, third explains all three parameters with defaults. Front-loaded and no unnecessary words.

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?

Given no output schema, description sufficiently explains return format (lines with roles and accessible names, indented). All parameters are described with defaults and behavior. Maps well to tool complexity and sibling context.

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 coverage is 100% (baseline 3), but description adds value: explains filter keeps matching lines with their indent, gives default values for maxLines (400) and selector ('body'), and clarifies selector roots the snapshot.

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?

Explicitly states it returns accessibility-tree snapshot of reportView page, comparable to browser_snapshot, for structure discovery when selectors drift. Clearly differentiates from siblings like pbi_deep_snapshot by specifying it returns ARIA snapshot with roles and accessible names.

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?

Provides context for when to use: 'for structure discovery when a selector drifts.' Although it doesn't explicitly list alternatives or when not to use, the use case is clearly implied, guiding the agent appropriately.

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