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

No annotations are provided, so the description carries the full burden. It discloses async behavior (returns {id, status}, poll getApiJob), credit handling (held, refunded on failure/cancel, 0.5 credits per result), and output shape (array with url and applied angles). It also states the 'same character and pose' reuse and sprite-only limitation, which are behavioral traits not in the schema.

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 long but front-loaded with purpose and constraints before alternatives and job semantics. Most sentences add unique value, though the parameter summary partly repeats what the schema already documents. For a complex async tool with credit implications, this length is justified.

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?

Despite having no output schema, the description fully describes the return value, async polling, credit cost, and API contract link. It gives enough context to call safely and to select among 30 sibling tools, including the sprite-type limitation and alternative tool routing.

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 the baseline is 3. The description adds meaning beyond the schema: image as URL or base64, camera_elevation omitted preserves current, n sets variation count, and request_id enables retrieval via listGenerations. It doesn't substantially enrich every field, but it provides a useful summary that helps the agent select values confidently.

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: 'Re-render an existing sprite from a different camera viewpoint while keeping the same character and pose.' It also names sibling alternatives (generatePose, animateSprite, transferMotion), so an agent can distinguish rotateSprite from nearby tools.

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?

It explicitly says 'Use this to produce alternate view angles of a character' and tells when to use alternatives: 'use generatePose instead to change the character's pose..., and animateSprite or transferMotion to bring a sprite to life.' It also constrains input types to sprites only, reducing misuse.

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