Create image render

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

With no annotations, the description carries behavioral burden. It states it queues an async job and returns a jobId, but doesn't disclose side effects (e.g., no resource modification), rate limits, or auth requirements. Adequate but not rich.

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?

Four sentences, each earning its place: main action, overrides, return value, usage alternative. Front-loaded with key verb and resource. No redundancy.

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?

Covers purpose, return, and a usage scenario. Lacks mention that at least one of payload or template should likely be provided (no required params in schema). No output schema, but return described as jobId. Good for a 5-param tool with full schema descriptions.

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%, so baseline 3. The description adds value by summarizing key overrides (snapshotTime, quality, transparent) and clarifying the two modes (payload vs template) beyond schema descriptions. Doesn't explain interaction between payload and template when both provided.

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 it queues a still-image render (PNG/JPEG) from a project JSON or image-type template, distinguishing it from sibling tools like create_render (likely video) and create_bulk_render. The verb 'queue' and resource 'still-image render' are specific.

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?

Provides explicit guidance: for new creative stills, first use find_matching_examples and start_from_example instead of composing from scratch. Also mentions polling with get_render. Lacks explicit when-not-to-use (e.g., video renders), but the name implies image-only.

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