view.set

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, and the description's 'Risk: read' is consistent with them. It adds useful operational context around the required VIEW_3D area and session policy, but it does not explain what observable effect setting the view has. There is no contradiction with the annotations.

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 text is compact and front-loads risk and requirements without filler. However, this conciseness comes at the expense of the core semantic content: the description is effectively just a command name plus metadata and does not define the operation.

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 description includes a useful environmental requirement and risk classification, but it omits the essential meaning of view.set and the valid values for the view parameter. Even with an output schema present, the agent lacks enough information to invoke the tool correctly.

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 main required parameter, view, is documented only as a bare string in the schema with no enum, format, or description. The tool description adds no explanation of what values the view parameter accepts or what the parameter means, so the agent must guess. Schema coverage is low and the description does not compensate.

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 identifies the tool only as 'PartMe Blender Harness command `view.set`' and then gives risk/requirements. It never states what action view.set performs, so it mostly restates the tool title without adding functional meaning. An agent cannot distinguish it from blender_view_focus or blender_view_present based on this description.

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?

It provides a precondition: a foreground window with a VIEW_3D area must exist. However, it gives no guidance on when to choose this tool instead of sibling tools such as blender_view_focus or blender_view_present, and it does not state the intended use case.

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