zoom_extents

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only states the action without confirming that the operation is view-only and does not modify the drawing, nor does it address edge cases like empty drawings. The description adds little beyond the tool name.

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, front-loaded sentence with no redundant words. It is appropriately sized for the tool's simplicity, and every word contributes to the meaning.

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?

The tool is very simple with no parameters and has an output schema, but the description lacks context about the effect (e.g., fitting all entities into the viewport) and assumes understanding of 'extents'. Given the absence of annotations, a bit more detail would improve completeness, but the description is minimally adequate for such a trivial operation.

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 and the schema confirms this with an empty properties object. With 0 parameters, the description has no need to explain parameter semantics, which aligns with the baseline of 4.

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 specific verb 'Zoom' and clearly identifies the target resource 'drawing extents'. It distinguishes the tool from siblings like zoom_window, which zooms to a user-defined window, and regen, which regenerates the drawing.

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 action 'Zoom to drawing extents' implies the use case of fitting the entire drawing into view, but the description does not explicitly state when to use this tool versus alternatives like zoom_window or view_plan. No alternatives or exclusions are mentioned, so the usage guidance is only implied.

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