Create Viewport

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

Beyond the sparse annotations (only destructiveHint=false), the description discloses important behavioral details: the viewport centers on the given model-space point and the view height is determined by height/scale. This adds real context about how parameters affect the resulting viewport without contradicting the annotation.

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 two concise sentences with no filler. It front-loads the core purpose and then provides the single most important formula for understanding how the viewport is computed.

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 moderate 8-parameter complexity, full schema coverage, and presence of an output schema, the description covers the essential behavior well. It could mention prerequisites like requiring a valid existing layout, but the current description plus schema is adequate for an agent to call the tool correctly in most cases.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining the relationship between scale, height, and view_center_x/view_center_y. The formula 'view height = height / scale' clarifies semantics that parameter descriptions alone do not fully convey.

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 opens with a specific verb and resource: 'Place a scaled model-space viewport on a paper-space layout.' This clearly identifies the tool's function and distinguishes it from sibling tools like viewport_set_scale, viewport_lock, and viewport_delete, which operate on existing viewports.

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 explains how the tool behaves but provides no guidance about when to use it versus alternatives. It does not mention that this is for creating a new viewport as opposed to modifying an existing one, nor does it reference viewport_set_scale or any prerequisite such as the layout needing to exist.

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