Set Viewport Scale

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 traits: annotative text/dimensions do not resize, and the main viewport is refused. This adds meaningful context about side effects and edge cases, though it does not cover all possible failure modes or state changes.

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 three concise sentences, front-loaded with the primary action and immediately followed by essential limitations. Every sentence adds value with no redundancy or filler.

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 presence of an output schema and moderately complex behavior, the description sufficiently covers purpose, limitations, and an edge case (main viewport refusal). It does not explain error behavior in detail, but it is complete enough for an agent to select and invoke the tool 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?

The schema already provides 100% coverage for both parameters (handle and scale) with clear descriptions. The description adds the context that rescaling adjusts 'view height' and clarifies the geometric nature, but it does not need to add much parameter detail, so a baseline 3 is appropriate.

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: "Rescale a viewport by adjusting its view height." This clearly identifies the tool's function and mechanism, distinguishing it from sibling viewport tools like viewport_lock or viewport_delete.

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 provides clear context on what the tool does and explicitly notes limitations: it only applies geometric scale and refuses the main viewport. However, it does not explicitly name alternative tools for other viewport operations, making the usage guidance strong but not fully explicit about alternatives.

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