Read or move the current camera

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

Annotations already declare a mutating, non-idempotent, destructive write profile, and the description corroborates and enriches this: it emphasizes WRITES LIVE GAME STATE, clarifies the write is confined to the local camera, notes idempotency=contextual-write, and states that existing properties are returned so the change is auditable. It also points at assert-state for verification. This is well beyond what the structured fields alone convey.

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?

It is front-loaded with the key mutating warning, which is good, but it is padded with a full Signature block that duplicates the input schema and a boilerplate tail (Phase/cost/Produces/Verify/Safety/On failure) that repeats the opening 'writes live game state'. Several sentences do not add information beyond the schema and annotations.

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?

There is no output schema, and the description compensates by noting that existing camera properties are returned for auditability, and by specifying prerequisites, idempotency, and a verification path. It is complete enough for a 7-param, nested-object mutation, though return-shape detail is only summarized.

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 100%, so the baseline is 3. The description adds cross-parameter semantics the schema does not: setCFrame requires position plus either lookAt or rotation in degrees. That constraint reasoning is genuinely useful beyond the per-field descriptions.

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 names a specific resource (the active/CurrentCamera) and concrete operations (read, set CFrame/position/look-at/FOV/CameraType). It even scopes it against the environment by stating it only changes the local CurrentCamera and does not move the character. An agent can tell exactly what this tool does and how it differs from generic instance/character tools.

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?

Explicit routing is given: action=get for a one-shot read, action=setCFrame for movement, with preconditions (requires active-client and explicit-mutation-approval). It also states what the tool is NOT for (no character movement, no server replication). It stops short of naming a specific alternative sibling tool for those excluded cases, so it falls just under fully explicit.

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