Dolly Camera Out

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

Annotations are absent, so the description must fully convey behavioral traits. It only states the basic effect, omitting details like whether the movement is relative/absolute, if there are limits, or if it is reversible. No mention of side effects or camera constraints.

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?

Single sentence, no redundant words. It is appropriately sized for a simple action, though a brief note on default behavior could fit without bloat.

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 the simplicity (1 optional param, no output schema), the description covers the basic action but lacks context on how this tool fits with camera control siblings (e.g., relation to dolly_camera_in, or effect on other camera parameters). An agent might need more for effective chaining.

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% with one parameter 'amount' documented in the schema. The description adds no additional meaning beyond the schema, such as default behavior or units. Baseline 3 is appropriate.

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 action (move camera farther) and resource (camera/subject). It uses cinematic terminology 'dolly out' which is specific and distinguishes it from sibling tools like dolly_camera_in. The verb+resource+scope pattern is strong.

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 on when to use this tool over alternatives like dolly_camera_in or dolly_camera. The description does not specify context, prerequisites, or exclusion criteria. An agent must infer usage solely from the name and basic action.

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