set_camera

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'configure' without explaining whether the scene state is mutated, whether other camera properties are reset, or what side effects occur. This is insufficient for an unannotated mutation-like 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?

The first sentence is concise and front-loaded, but the second sentence 'IMPORTANT: Always use MCP tools for scene operations' is generic filler that does not earn its place for this specific tool. It adds noise without useful tool-specific detail.

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?

With only two parameters and full schema coverage, the description is mostly sufficient, but it lacks behavioral context and usage guidance. The presence of an output schema reduces the need to explain return values, but the missing mutation context and generic instruction leave the description incomplete.

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 100%, so the description adds little beyond the schema. The phrase 'position and/or orientation' clarifies that both are optional and can be set independently, but this is minimally additive.

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 identifies the tool's purpose with a specific verb and resource: 'Configure the camera position and/or orientation.' No sibling tool performs this function, so it distinguishes itself naturally.

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 given on when to use set_camera versus alternatives like move_to or align_to. The 'IMPORTANT' sentence is a generic instruction about using MCP tools, not a tool-specific usage guideline.

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