view_plan

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

With no annotations provided, the description carries the burden. It discloses the exact behavior: returning to top, wireframe, and zoom extents view. This is a complete behavioral description for a view-change operation, though it does not discuss potential side effects (e.g., whether it resets other viewport settings).

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 two sentences with no filler. The first sentence states the action and the second gives usage context. It is front-loaded and efficient.

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 simple view command with no parameters and an output schema, the description fully covers its purpose, behavior, and usage context. It integrates well with the sibling set by clarifying its role versus 3D and zoom tools.

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-level documentation is needed. The baseline for zero-parameter tools is 4, and the description adds no unnecessary detail about parameters.

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 the tool's function: 'Back to flat 2D view (top, wireframe, zoom extents).' This uses specific verbs and resources, and distinguishes it from siblings like view_3d (which switches to 3D) and zoom_extents (which only changes zoom).

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 'Use after 3D work' provides clear contextual timing for this tool. It does not explicitly name alternatives or exclusion conditions, but the context is sufficient for an agent to know when to invoke it relative to 3D operations.

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