setup_camera_3d

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

With no annotations provided, the description carries the full burden. It discloses critical behaviors: fov and rotation are in degrees, look_at is a world-space target, and reconfiguring is not undoable. These go beyond the schema and help the agent understand consequences.

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?

The description is a single semicolon-separated sentence that is front-loaded with the purpose and followed by essential parameter clarifications. Every clause is informative, with no redundant or unnecessary words.

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 tool's complexity (14 parameters, no output schema, no annotations), the description is insufficient. It covers only a few key parameter details and omits explanations for most parameters, behaviors like return values, and error handling. An agent would struggle to use it correctly without additional information.

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?

The description adds meaning for only three parameters (fov, rotation, look_at). With 14 parameters and 0% schema coverage, the other 11 parameters (far, near, size, current, cull_mask, projection, position, etc.) are left unexplained, failing to compensate for the schema 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 clearly states the tool's function with a specific verb and resource: 'Create or reconfigure a Camera3D'. It also provides key details about the parameters (degrees, world-space target), distinguishing it from generic sibling 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?

The description clearly implies when to use the tool: when creating or reconfiguring a Camera3D. It also warns about non-undoable reconfiguration, adding context. However, it does not explicitly mention alternatives or when not to use it.

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