Lock Viewport

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

The description clearly states that the tool toggles the lock state of the viewport's display scale, which is the core side effect. However, annotations do not provide read-only or destructive hints, and the description does not explain consequences such as whether locked viewports ignore scale changes or whether the operation is reversible beyond calling this again.

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?

A single sentence with no redundant words; the key scope ('display scale') is placed immediately after the verb. Every word earns its place, and it is easily scannable.

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?

For a two-parameter boolean toggle with an output schema and fully described parameters, the description covers the essential operation. It still leaves the implication of a locked viewport unstated and lacks alternative routing, but these gaps are minor for such a simple tool.

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 input schema already fully describes both parameters: handle's source is given and locked's meaning/default is explicit. The description adds no additional parameter detail, so it sits at the baseline for 100% schema coverage.

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 uses a clear verb pair ('Lock or unlock') with a specific resource ('a viewport's display scale'), which is more specific than the title. This distinguishes it from sibling viewport_set_scale, which would set the scale value rather than toggle its lock state.

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?

No guidance or conditions are given: the description does not say when to choose this over viewport_set_scale or viewport_list, nor mention prerequisites such as the handle referring to an existing viewport. The intended use is only implied by the action itself.

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