view_set_preset

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

Annotations only declare readOnlyHint=false; the description earns credit by disclosing the actual side effect (camera viewpoint changes to a preset angle) and that inputs are allowlisted rather than free-text. It goes beyond the annotation without contradicting it.

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?

Three short, labeled lines with the core action front-loaded and no filler. Slightly terse, but every sentence carries information.

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?

A small, single-parameter mutation tool with an output schema and full schema documentation; the description covers purpose and side effect adequately. Only a clearer relationship to view_set_direction/view_zoom_extents 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?

Schema coverage is 100% and the schema already enumerates all ten preset strings with a default, so the description only needs to point at the concept. It adds the illustrative 'se_isometric' example, but no extra semantics about case, invalid values, or axis conventions beyond 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 names a specific verb and resource (apply a 3D view preset) and scopes it with 'allowlisted orthographic or isometric', so an agent knows exactly what operation it performs. It doesn't explicitly contrast with view_set_direction, but 'preset' vs. typed vectors plus the 'se_isometric' example give a reasonable signal.

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 'Disambiguation: Fast standard view alignment' line implies this is the quick path for standard angles, but no sibling is named and no when-not condition is given. An agent must infer the boundary with view_set_direction on its own.

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