viewport_zoom_extents

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

Annotations already mark the tool as non-read-only and destructive, so the description only needs to add context. It does reveal that the operation affects all viewports and that the selection flag changes the framing target. However, it does not warn that current viewport/camera framing will be overridden or explain what happens when selection=true but nothing is selected.

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 and front-loaded with the primary action, followed by the parameter behavior. The bilingual duplication is somewhat redundant but serves two language audiences, and every distinct unit of information earns its place.

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 one-parameter viewport command with annotations and full schema coverage, the description is largely complete: it states the target (all viewports), the behavior (zoom to fit), and the selection handling. Minor missing edge cases include no active selection behavior and whether the view change is undoable, but these are not critical for a simple zoom command.

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 documents the single boolean parameter with full coverage, including its default value. The description repeats the same meaning ('selection=true frames only the current selection, otherwise the whole scene') without adding details beyond the schema, so it meets the baseline but adds no extra value.

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 a specific action and resource: 'Zoom all viewports to fit' in both Chinese and English. It distinguishes itself from sibling viewport tools like viewport_set_view or viewport_capture by identifying the zoom-to-extents behavior and the selection scope toggle.

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 clear conditional context: use selection=true to frame the current selection, otherwise frame the whole scene. It does not explicitly name alternative tools or when not to use it, but the behavioral context is clear enough for an agent to decide when this tool applies.

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