Delete Viewport

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

The annotations already indicate destructiveHint=true, and the description adds substantial behavioral context: it explains that deleting the main viewport requires force, that it removes the tab's own view state, and that the current-viewport pointer is repaired to avoid dangling references. This exceeds what annotations alone provide.

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 concise: one short sentence plus one informative sentence. Every clause adds value, with no redundant phrasing or repetition of what is already in the schema.

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 destructive annotation, full schema coverage, and presence of an output schema, the description covers all necessary context: the main viewport edge case, the pointer repair, and the force requirement. No critical information 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% for both parameters, so the baseline is 3. The description adds meaning to the `force` parameter by explaining when it is necessary and what happens if it is not set, which goes beyond the schema's default value description.

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 clearly states 'Delete a viewport' using a specific verb and resource. It distinguishes from sibling viewport tools (viewport_create, viewport_list, viewport_set_scale) by focusing on deletion.

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 important context on when the `force` parameter is required (deleting the layout's main viewport) and explains consequences, but does not explicitly mention alternative tools or when not to use it. Still, it gives clear usage guidance beyond the basic operation.

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