point_camera_at

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

With no annotations, the description carries the full burden. It usefully discloses that the tool works by creating a Track To constraint, but it omits key side effects: whether an existing constraint is replaced, whether the camera's prior rotation is overwritten, and any reversibility. This is meaningful but incomplete disclosure for a mutation tool.

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?

Front-loaded with the core action, then a compact Args block and a brief Returns line. No redundant sentences, though the Returns line adds little since an output schema exists.

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?

An output schema exists so return values needn't be detailed, and parameters are covered. However, for a mutation tool with zero annotations, the description should disclose side effects (constraint replacement, rotation overwrite) and does not, leaving a real gap.

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 0%, so the description must compensate, and it does: it explains target as an object name, location as [x, y, z], and the mutual exclusivity between them. It leaves out the documented defaults (target="", location=null) but covers all three parameters' intent well.

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 verb and resource ('point a camera') plus the mechanism ('Track To constraint'), which makes the effect concrete. It does not explicitly contrast with close siblings like set_camera_from_view or set_active_camera, so it falls short of a 5.

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 gives one real usage rule — target and location are mutually exclusive — which helps an agent pick a call form. It offers no guidance on when to prefer this over set_camera_from_view or other camera orientation tools, so usage is only implied.

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