camera_add

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

No annotations are provided, so the description carries the full burden. It describes the inputs and outputs (success/error) but does not disclose side effects (e.g., making the camera current might affect the scene's active camera) or error conditions (e.g., invalid paths). The behavioral traits are partially covered but not exhaustively.

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 well-structured: a one-line summary, category, bulleted arguments with clear descriptions, and a returns line. It is front-loaded with the purpose and uses no unnecessary words, making it efficient for an agent to parse.

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?

The description covers all 6 parameters, includes return value behavior, and is sufficient for a simple creation tool. However, it omits mention of constraints like path existence or project loading state, which could affect success. With no annotations, it is reasonably complete but not exhaustive.

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?

With 0% schema coverage, the description provides all parameter meaning beyond the schema's titles. It clarifies the expected value types (e.g., 'Camera2D or Camera3D' for camera_type) and defaults (make_current defaults to True). This adds significant value over the raw schema.

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: 'Add a camera node to a scene.' It includes the category 'Camera' and lists specific parameters that distinguish it from sibling tools like node_add or camera_set_properties. The verb 'Add' and resource 'camera node' are precise and unambiguous.

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 does not explicitly state when to use this tool versus alternatives like node_add or other camera-related tools. It implies usage when adding a camera to a scene but lacks guidance on prerequisites or exclusions (e.g., requiring an existing scene). No comparison with sibling tools is provided.

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