point_camera_at

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

With no annotations provided, the description carries the full disclosure burden. It usefully reveals that use_constraint creates a Track To constraint for continuous follow, implying the non-constraint path is a one-time orientation. However, it doesn't disclose what the non-constraint mode does to the camera (rotation modification, constraint removal, coordinate space) or any side effects.

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 two-clause sentence that front-loads the core purpose before the constraint detail. Zero wasted words; every phrase adds meaning, and the primary function is immediately visible.

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 3-parameter tool with no output schema, the description covers the essential purpose and the constraint toggle. Gaps remain: coordinate space expectations, non-constraint behavior details, and whether any camera object works or only the active one. Adequate but with notable omissions.

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. It clarifies target accepts either an object or coordinate array ('对象或坐标') and explains use_constraint's role. The camera parameter receives no semantic explanation, and the expected coordinate format (world space, units) is unspecified, leaving a partial compensation for the coverage gap.

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 states a specific verb (point/朝向) with a clear resource (camera) and target flexibility (object or coordinates), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like point_light_at or set_camera, relying on the name for distinction.

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 explains the use_constraint behavior but provides no guidance on when to choose this tool over alternatives such as set_camera, frame_objects, or point_light_at. No exclusions, prerequisites, or routing conditions are given; usage context must be inferred entirely from the name.

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