Delete Viewport

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

The annotations already flag destructiveHint=true, so the description does not need to restate basic destructiveness. It adds valuable behavioral detail: deleting the main viewport removes the tab's own view state and repairs the current-viewport pointer to avoid dangling references. This goes well beyond the annotation and helps the agent anticipate side effects.

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 extremely concise: one clear action sentence followed by a focused caveat about the main viewport. There is no redundant phrasing or filler, and the most important operational detail is front-loaded.

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 two parameters, full schema coverage, destructiveHint annotation, and existing output schema, the description covers the essential edge case that would otherwise surprise an agent. Nothing critical for correct invocation is missing.

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. The description adds meaningful context for the force parameter by explaining that the main viewport needs force=true and describing what happens when it is deleted. This reinforces the schema description and helps the agent understand when and why to set force.

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 — 'Delete a viewport.' This clearly distinguishes the tool from sibling viewport tools such as viewport_list, viewport_create, viewport_set_scale, and viewport_lock. No ambiguity remains about what action this tool performs.

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 gives a clear condition for a special case: the layout's main viewport requires force=true. This tells the agent when to set the force flag. It does not explicitly name alternatives or exclusions, but for a deletion tool with no near-equivalent sibling, the context is adequately clear.

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