bl_set_view

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 behavioral disclosure. It mentions that the camera is pointed and an image is returned, but it does not disclose that the current viewport state is changed, what the returned image contains, or how width, timeout, and frame_all affect behavior.

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 highly concise and front-loaded, with the core purpose stated first and the direction values listed immediately after. No filler or redundancy exists, though the brevity leaves little room for needed guidance.

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 tool with four parameters, no annotations, no output schema, and sibling tools like bl_screenshot, the description is incomplete. It omits parameter semantics for three parameters, side effects, return value details, and any selection guidance among siblings.

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 description coverage is 0%, so the description must compensate for undocumented parameters. It adds meaning only to 'direction' by listing valid values; width, timeout, and frame_all remain entirely unexplained.

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 states a specific action: point the viewport camera along one axis and return the image. It is clear and names the key 'direction' parameter, but it does not explicitly differentiate itself from the sibling tool bl_screenshot, which also returns an image.

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?

There is no guidance on when to use this tool versus alternatives such as bl_screenshot. The description lists direction options but provides no context about prerequisites, sequencing, or cases where another tool should be preferred.

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