Render an Agent-visible preview

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

The description discloses that temporary previews are deleted after embedding, which is a non-obvious behavioral detail beyond the readOnly/idempotent/non-destructive annotations. It also explains that an optional output path preserves a copy, aligning with the schema's 'never overwrites' guarantee.

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 two sentences, front-loaded with the primary action, and the second sentence efficiently conveys the temporary-file lifecycle. No superfluous content.

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 tool has 7 parameters and an output schema, so the description need not detail returns or every parameter. It covers the two most important behavioral caveats—temporary deletion and optional persistence—while annotations and schema cover the rest, making it sufficiently complete.

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 coverage is 100% and the description adds no parameter-specific syntax beyond what is already in the input schema. The phrase 'safe output path preserves a copy' mirrors the schema's outputPath description, providing no additional semantic 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 renders a bounded PNG preview from an existing scene and returns it directly as MCP image content. This specific verb-resource-output combination distinguishes it from sibling render tools like keyshot_render or keyshot_batch_render, which likely produce full-resolution files.

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 the tool is for bounded previews delivered as image content, which fits quick visual checks, but it does not explicitly compare to sibling tools or state exclusions. The context is clear but lacks direct guidance such as 'use this instead of keyshot_render for fast previews.'

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