get_viewport_screenshot

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

With no annotations provided, the description fully covers behavioral traits: it describes the snapshot process, camera and rendering modifications, the ensure block for restoration, and the order of operations. This gives the agent complete transparency.

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 a concise purpose, a bulleted parameter list, and a note on operation order. Every sentence adds value without redundancy.

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 complexity (5 parameters, view mutation), the description covers purpose, parameters, operation order, restoration safety, and return type (MCP Image). No gaps remain, even without an output schema.

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 description coverage is 0%, but the description explains each parameter in detail, including constraints (e.g., max_size range, aspect ratio), enums (view_preset, style), default behavior (current, default), and the restore_view mechanism. This fully compensates for the lack of schema descriptions.

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 'Capture the current SketchUp viewport as a PNG and return it as an MCP Image.' This is a specific verb-resource-output combination, and it is distinct from sibling tools (all modeling operations).

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 says 'Useful for letting Claude visually verify the scene between steps,' providing a clear use case. It does not explicitly list when not to use or alternatives, but the context and parameter explanations offer sufficient guidance.

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