workspace_snapshot

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

The description discloses that the tool resets diffMode buffer and identity tracker as side effects, runs internally in parallel, and has latency equal to max single screenshot. It warns about scaled thumbnails and suggests recording a step for tracking reset points. All behavioral traits are well documented, and there are no annotations contradicting them.

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 well-structured with sections (Purpose, Details, Prefer, Caveats) and front-loaded with purpose. While it is relatively long, every sentence contributes meaningful information without redundancy. Could be slightly trimmed but remains efficient.

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, the description thoroughly explains all return values (thumbnails, uiSummary with action, clickAt, value). It covers side effects, performance characteristics, usage scenarios, and even a reference to causal trail recording. The description is highly complete for the tool's complexity.

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 input schema covers all three parameters with clear descriptions (100% coverage). The description adds context beyond schema by explaining the output format (uiSummary.actionable) based on includeUiSummary, and the parallel execution behavior, but does not elaborate much on individual parameters beyond what schema provides. The added value is moderate.

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 that the tool returns display layouts, window thumbnails, and per-window actionable element lists, using specific verb 'Orient' and resource 'workspace'. It distinguishes from siblings like screenshot by mentioning cheaper alternatives and different use cases.

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 explicitly provides when to use this tool ('session start or after major workspace changes') and when not ('use screenshot(detail='meta') for cheap re-orientation', 'screenshot(detail='text', windowTitle=X) for single-window update'). It also gives caveats about scaled thumbnails and side effects.

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