blockbench_set_camera

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

With no annotations provided, the description must disclose behavioral traits. It only states 'set' without indicating side effects, state changes, or constraints. For example, it does not mention whether the change is persistent, affects subsequent captures, or requires specific permissions. This is insufficient for a tool with 4 parameters.

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 sentence, achieving conciseness. However, it is overly terse, sacrificing informative content. It could be expanded without becoming verbose. The structure is front-loaded but lacks necessary details.

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?

Given 4 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to specify parameter effects, defaults, or return behavior. An AI agent would lack essential context to correctly invoke the tool, especially for the required 'position' parameter.

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 schema has 0% description coverage, so the description must explain parameters. It provides none. The four parameters (position, fov, target, orthographic) are not mentioned, leaving the agent to guess their meaning and usage from names alone. This is a critical gap.

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 action ('Set the active Blockbench preview camera') and its intended context ('before visual inspection'). It effectively conveys the primary purpose. However, it could be more specific about what 'preview camera' entails, especially distinguishing it from other camera-related operations in siblings like blockbench_capture_preview.

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 description provides no guidance on when to use this tool versus alternatives. While it implies use before visual inspection, it does not explicitly say when not to use it or mention any prerequisites or alternatives among the siblings. This lack of usage context leaves the agent to infer appropriateness.

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