List camera presets

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds behavioral context by specifying that it reads a JSON configuration and does not open KeyShot. This goes beyond the structured hints, but could further explain failure modes (e.g., missing/invalid JSON) or the difference between 'standard' and 'absolute' presets.

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 well-structured sentence that front-loads the action ('Read... return...') and includes all essential information without filler. Every word contributes to understanding the tool's purpose and behavior.

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 zero-parameter read-only tool with an output schema and strong annotations, the description is complete. It states the input source (configured JSON), the operation (return presets), and the key constraint (without opening KeyShot). No additional return-value documentation is needed since an output schema exists.

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 tool has zero parameters, and the schema is trivially fully described. With no parameters to document, the description doesn't need to provide parameter-level details. Given the 0-param baseline of 4, this is appropriate.

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?

Description clearly states it reads the configured camera preset JSON and returns valid standard or absolute camera presets, with the key qualifier 'without opening KeyShot'. This distinguishes it from other camera-related tools like keyshot_list_cameras (which likely lists scene cameras) and keyshot_apply_camera_preset (which applies presets).

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 phrase 'without opening KeyShot' provides clear context for when this tool is appropriate: when you need to inspect available presets without launching the application. However, it doesn't explicitly name alternatives or state when not to use it, such as clarifying that keyshot_list_cameras is for current scene cameras.

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