ac_camera_mode

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

With no annotations, the description carries the full burden; it does disclose a meaningful side effect, that the currently held camera is released, which is real context beyond a bare mode setter. It says nothing about what happens with an invalid mode string, whether the simulator must be running, or whether the change is immediate or requires a rendering tick.

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?

A single compact sentence that front-loads the action and then enumerates values; the hotkey hints are short and genuinely useful rather than filler.

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 one-parameter command tool with no annotations and no output schema, the description covers the action and the complete value domain, which is the critical information. It stops short of describing the response or failure behavior, which would be worth a clause given there is no output schema.

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 0% with no enum on 'mode', so the description must supply the value domain, and it does: free, cockpit, chase, chase2, bonnet, car, track, release, with parenthetical notes for free (F7), car (F6) and track (replay cams). It omits case sensitivity and whether an unknown value errors or is ignored, which keeps it below a 5.

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?

States a specific action (release held camera and switch AC camera) plus the full set of accepted modes, so the resource and operation are unmistakable. It implicitly differentiates from siblings like ac_camera_free by folding 'free' and 'release' into this tool's mode vocabulary, though no sibling is named directly.

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?

'release' is annotated as 'only let go of the held camera', which hints at the choice between full mode switching and merely dropping the held camera. However, there is no explicit guidance on when to use this versus ac_camera_free, ac_camera_look_at, or the F6/F7 hotkeys directly, and no preconditions are stated.

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