Capture the current SketchUp view as an image without specifying an output path, then inspect it to visually verify your model after changes.
See the current SketchUp view directly as an image. No output path required. Use after modeling to visually verify the result.
| Name | Required | Description | Default |
|---|---|---|---|
| width | No | ||
| height | No | ||
| model_id | No | ||
| active_path | No | ||
| transparent | No |
Changes observed during successful MCP inspections.
v1.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context that the image is returned directly rather than written to a path, but says nothing about image format, resolution limits, or what happens with the viewport.
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?
Three short sentences, front-loaded with the core action, with no filler. Every sentence contributes (purpose, output behavior, usage timing).
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 five undocumented parameters and no output schema, the description leaves real gaps. It covers purpose and timing adequately for a simple capture tool, but a caller cannot know how to size the image or what model_id/active_path do.
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% across 5 parameters (width, height, model_id, active_path, transparent), and the description mentions none of them. An agent must guess at the meaning of model_id, active_path, and transparent entirely from their names.
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?
States a specific verb and resource: capturing the current SketchUp view as an image. The phrase 'No output path required' implicitly contrasts it with file-writing siblings like view_export, but it never names that sibling, so differentiation is left to inference.
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?
'Use after modeling to visually verify the result' gives a clear when-to-use context, which is better than nothing. However, it does not name alternatives such as view_export or model_snapshot, nor state when this tool is the wrong choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.