move

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

No annotations are provided, and the description merely restates the basic action without adding behavioral details. It does not mention coordinate frame, sign conventions, whether movement is relative or absolute, or what happens when distance is omitted.

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 concise sentence with no filler or redundant information. It is appropriately front-loaded, though it is so terse that it borders on under-specification.

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 camera-move tool with full schema coverage and an output schema, the minimal description is arguably sufficient. However, the lack of behavioral context and usage alternatives leaves it adequate but with clear gaps in completeness.

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 input schema provides 100% coverage, including descriptions for both axis ('x', 'y', 'z') and distance ('Angstrom') with a default value. Since the schema already explains the parameters clearly, the description adds no extra semantic value, so the baseline score of 3 applies.

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 uses a specific verb ('Moves') and resource ('camera along an axis'), making the primary function clear. It does not explicitly distinguish itself from sibling camera tools like turn, orient, or zoom, but the translational nature is implied by 'along an axis'.

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 given on when to use this tool versus alternatives such as turn, orient, zoom, or center. There are no contextual cues, prerequisites, or exclusions, leaving the AI agent to guess based on the name alone.

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