snapshot_request

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals a key behavioral trait: 'Returns immediately,' indicating an asynchronous operation. It also implies the image is not immediately available, which is important context. However, it does not mention potential failure modes, session-specific behavior, or what the immediate return value signifies.

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 a single, front-loaded sentence that delivers all necessary information without fluff. Every phrase contributes: the action, the immediate return behavior, and the follow-up step. It is concise and well-structured.

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 the tool's simplicity (one optional parameter, no output schema), the description covers the core workflow of capture-then-read. However, it lacks any explanation of the 'session' parameter and does not describe the immediate return value or success/failure signaling. The missing parameter semantics and return info leave gaps for an agent to make correct calls.

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 schema has one parameter 'session' with zero description coverage. The description does not mention this parameter at all, providing no semantic meaning beyond the type 'string.' An agent has no way to infer what 'session' should contain or how it affects the capture, making this a significant gap.

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 a specific action: 'capture the shared screen.' It distinguishes itself from the sibling tool snapshot_read by explicitly noting the image must be read later via snapshot_read, making the purpose and relationship unambiguous.

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 provides explicit usage guidance by stating 'read the image with snapshot_read on a later turn.' This tells the agent exactly when to use this tool (to request capture) and when to use the alternative (to retrieve the image), fulfilling the need for when-to-use vs alternatives.

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