List scene cameras

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the contextual note 'without saving changes', which reinforces that opening the scene will not persist modifications. This is useful but not extensive, and it aligns with annotations, so a mid-range score is appropriate.

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 composed of two concise sentences: the first states the core function and the second provides contextual usage. Every word earns its place, and the main action is front-loaded, making it clear and efficient.

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 list tool with one parameter, the description covers purpose and usage, while the output schema and annotations handle return values and safety. The description also clarifies the non-mutating behavior, making it complete for the tool's complexity.

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%, with the scenePath parameter fully described as an absolute path to an existing KeyShot scene file, including a note about paths outside the output directory. The description does not add any parameter-specific details, so it relies on the schema, which already carries the semantic weight.

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 verb 'Return' and the resource 'saved camera names', and adds the qualifier 'without saving changes' to clarify the non-destructive nature. This distinguishes it from sibling tools like keyshot_set_camera or keyshot_render_all_cameras, which perform different actions.

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 explicitly advises using this tool 'before selected-camera rendering when names are unknown', providing a clear usage context. It does not explicitly name alternative tools, but the guidance implies where this fits in a workflow, which is sufficient for a straightforward list operation.

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