view_3d

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

No annotations are present, so the description must disclose behaviors. It does mention 'Zooms extents,' a side effect, and lists valid values. However, it does not clarify whether the view change affects only the current viewport or if any drawing state is modified.

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 semicolon-separated lists. Every word adds value; no padding or repetition.

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 tool with two optional params, the description covers the main options and the zoom extents side effect. An output schema exists, so return values need not be described. Minor omissions like the meaning of 'iso2' are acceptable for this simplicity.

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 0% and there are no enums, so the description compensates by listing allowed values for 'direction' and 'shade' (e.g., iso/top, wireframe/gouraud). This adds practical meaning beyond the bare schema, though defaults are left to the schema.

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: '3D view' and enumerates valid direction and shade options. This distinguishes it from siblings like view_plan (2D plan) and zoom_extents (zoom-only).

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?

No guidance is provided on when to use this tool versus alternatives. It simply lists parameters without explaining use cases or exclusions.

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