keyshot_render

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

With no annotations, the description carries the full burden. It only states the basic action without disclosing behavioral traits such as side effects (e.g., file creation, scene modification), required licenses, or hardware/software dependencies. The agent is left to assume safe behavior.

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?

While the single sentence is concise, it is too brief for a tool with 8 parameters and no annotations. The description does not provide enough useful information to warrant its length; it under-serves the complexity.

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?

The description is severely incomplete given the tool's complexity (multiple parameters, no output schema, no annotations). It omits information about return values, processing expectations, file size limits, and integration with the scene file. The agent cannot reliably invoke this tool based on the description alone.

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 0% and the description adds no information about the 8 parameters. The agent must rely solely on parameter names, which are insufficient for correct usage (e.g., 'samples' could be ambiguous). This is a critical gap.

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 (render) and resource (KeyShot scene to image file). It differentiates well from sibling tools like keyshot_batch_render and keyshot_save_scene. However, it could explicitly specify 'single render' to avoid ambiguity with batch rendering.

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 guidelines are provided about when to use this tool versus alternatives. The description does not mention prerequisites, typical use cases, or when to choose e.g., keyshot_batch_render instead.

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