screenshot

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context not present in the annotations: when a view is supplied, the camera changes only temporarily and the previous view is restored afterwards, which reassures the agent about side effects.

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 tight sentences with no filler. The core purpose is front-loaded, and the view behavior detail follows immediately after.

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?

With no output schema, the description correctly states that an image is returned. It covers the main invocation modes, though it omits image format and says nothing about the sizing parameters (max_size default 1024, width/height interaction), which would help an agent call it correctly.

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 75%, with 'height' undocumented, so the schema carries most of the load (baseline 3). The description adds meaning beyond that by explaining the view parameter's temporary-and-restored camera semantics, which is not captured by the schema's 'Temporary capture view' text.

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 names a specific verb and resource ('Capture the SketchUp viewport and return the image') and even states the motivation (so Claude can check modelling results). It is immediately clear what the tool produces, though it does not explicitly distinguish itself from siblings like export_png or set_view.

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 phrase 'to check modelling results' implies a usage context, and 'Empty view = keep the current view' clarifies a mode of invocation. However, there is no explicit guidance on when to prefer this over export_png or set_view, so usage is only implied rather than stated.

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