maya_create_camera

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 only states 'create a camera', which implies a mutating operation, but does not disclose side effects (e.g., new node added to scene, selection changes, or what happens to existing cameras). For a creation tool, this is insufficient.

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, well-structured sentence that is front-loaded with the action and key configurable attributes. No extraneous information, earning its place.

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 has an output schema, the description need not explain return values. It adequately conveys the basic operation but lacks completeness in terms of behavioral context and parameter details. It is minimally adequate.

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 mentions three of four parameters (position, look-at, focal length) but adds no detailed meaning beyond the schema's own descriptions. The name parameter is omitted. With schema description coverage reported as 0%, the description does not compensate by providing additional context.

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 action 'create a camera' and specifies configurable attributes (position, look-at, focal length). This distinguishes it from sibling tools like maya_create_light or maya_create_primitive. However, it could explicitly state that it creates a camera node in the Maya scene.

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?

No guidance is provided on when to use this tool versus alternatives, such as maya_import_file or maya_create_primitive. There is no mention of prerequisites like an open Maya scene or any context about when this tool is appropriate.

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