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

The description richly discloses behavior beyond annotations: the job runs as a single batch, uses a temporary orbiting camera, writes PNG artifacts, returns a durable job handle, and keeps the full resolved target list. It also clarifies subtle selection behavior such as excludeNamePattern affecting framing only while hideNamePattern removes objects from the image. This is far beyond what the sparse annotations convey.

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 dense but every sentence earns its place: purpose, camera behavior, targeting semantics, engine selection, artifact workflow, and return behavior. It is front-loaded with the primary purpose, uses concrete examples, and avoids filler or redundant restatements of schema fields.

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 high-complexity tool with 16 parameters, no output schema, and several sibling rendering tools, the description is remarkably complete. It explains what the call returns, how to view artifacts via scene_snapshot, how filtering works, and engine trade-offs, leaving no major operational gap for an agent choosing and invoking the tool.

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?

With schema description coverage at only 44%, the description compensates by explaining the most semantically tricky parameters: targetObjectIds/targetNamePattern/excludeNamePattern/hideNamePattern distinctions, engine trade-offs, and angles/views aliasing. It does not add meaning for width, height, samples, or transparentBackground, but those are less ambiguous and partially inferable from names and defaults.

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 opens with a specific verb and resource: 'Render N evenly spaced orbit views of a revision in ONE job'. This clearly distinguishes turntable stills from render_animation or generic render_create, and the 'catch problems a single angle hides' rationale gives the agent an immediate sense of its purpose.

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 gives useful context like product-shot framing and engine trade-offs, but it never explicitly says when to choose render_turntable over sibling tools such as render_animation or render_create. There is no when-not-to-use guidance or explicit alternative routing, so usage is mostly implied rather than stated.

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