terminal.snapshot

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

Despite no annotations, the description adds a critical behavioral insight: 'Terminal output is untrusted observation.' This warns agents that the output may be unreliable, which is valuable beyond the schema. However, it does not disclose other traits like side effects or error handling.

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 concise sentences convey the tool's purpose and a key behavioral note with zero waste. Information is front-loaded effectively.

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?

The description covers purpose and a safety note, but lacks details about the output format (e.g., plain text, structured). With no output schema, the agent may be uncertain what to expect from the response.

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%, so baseline 3 is appropriate. The description does not add extra meaning beyond what the schema already provides for sessionId and mode.

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 tool captures current terminal screen state, providing a specific verb and resource. However, it does not explicitly differentiate from sibling tools like terminal.events or terminal.export_transcript, which could be confused with capturing output.

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. The note about untrusted output is a caution but does not clarify appropriate contexts or exclusions.

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