Zoom Extents

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

The annotations already indicate the operation is non-destructive (destructiveHint=false) but not read-only (readOnlyHint=false), meaning it changes viewport state. The description reinforces that it modifies the current view to show all entities, but adds little beyond the annotations—such as whether it affects model space or paper space, or the exact zoom behavior.

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 a single sentence with a helpful parenthetical clarification. Every word earns its place, and the core behavior is front-loaded with no filler or repetition of the title.

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 tool with no parameters, an output schema, and clear annotations, this description is sufficiently complete. It tells an agent exactly what the tool does, and the sibling context provides enough differentiation from other view-related tools. Nothing essential 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?

The tool has zero parameters, so no parameter documentation is needed. The schema coverage is effectively 100% by having an empty parameter object, and the description adds no conflicting or missing information. This matches the baseline for a no-parameter tool.

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 states a specific action ('Zoom') and a precise resource/scope ('to show all entities in the drawing'), and the parenthetical 'fit drawing in viewport' clarifies the intended outcome. This is clearly distinct from sibling tools like view_zoom_window, which would zoom to a selected area rather than all entities.

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 phrase 'fit drawing in viewport' implies the use case: after changes or when the user wants an overall view. However, the description does not explicitly mention alternatives such as view_zoom_window or explain when this tool would be preferable, so the guidance is implied rather than stated.

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