keyshot_list_camera_presets

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It discloses that it reads from a specific file or environment variable, which is useful. However, it does not state that it is non-destructive or mention error states. Given the tool's simplicity, this is adequate but not fully transparent.

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 sentence that efficiently conveys the tool's purpose and data sources. It is front-loaded and contains no unnecessary words.

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 no parameters and no output schema, the description is sufficiently complete for a listing tool. It explains where the presets come from. It could optionally mention the output format, but this is not critical for an AI agent to select and invoke the tool correctly.

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, so the baseline score is 4. The description adds context about the data source, which goes beyond the schema. Since schema coverage is 100% (empty schema), the description provides additional value.

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 lists camera presets, specifying the sources (presets/cameras.json or KEYSHOT_CAMERA_PRESETS). It distinguishes from siblings like keyshot_apply_camera_preset and keyshot_list_cameras by focusing on presets vs. actual cameras or applying them.

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 implies that this tool is for listing camera presets, which is distinct from applying them or listing cameras. However, it lacks explicit guidance on when to use this tool versus alternatives like keyshot_list_cameras.

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