capture_view

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

Discloses behavior such as returning an image, zoom-to-fit option, and default document handling. With no annotations, the description effectively communicates the read-only nature of a screenshot, though it doesn't explicitly state safety.

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 brief and front-loaded with the core purpose; the argument list is structured and adds necessary detail without bloat. Every sentence earns its place.

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 the tool's purpose, parameters, a usage recommendation, and the output type. It doesn't specify the exact image format or return mechanism, but for a screenshot tool this is sufficient.

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?

Since the schema has no descriptions, the description fully compensates by enumerating all five parameters, providing allowed values for 'view', explanation for 'fit', defaults for width/height/document, and the purpose of each.

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 uses the specific verb 'Screenshot' and clearly identifies the resource as the 3D view, with the return value stated as an image. This distinguishes it from sibling tools and states exactly what the tool does.

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 explicit guidance to use the tool after building geometry to verify correctness ('Always look at the model...'), which tells the agent when to invoke it. It doesn't mention alternatives or when not to use it, but the context is clear.

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