render_character_review

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

With no annotations, the description carries the full burden. It does disclose that a new version is created (a side effect) and ties the output to an approval gate, but it omits whether the render is expensive/async, whether it requires permissions, what happens to prior versions, or how failures surface.

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?

A single front-loaded sentence with no filler. It is appropriately sized, though its brevity comes partly from under-specification rather than disciplined editing.

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?

An output schema exists, so return values need not be explained. But the definition leaves 7 undocumented parameters, no usage guidance, and no annotation-backed behavioral context for what appears to be a version-creating render operation. Too thin for the tool's complexity.

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% for 7 parameters, including required ones like project_root, character_id, source_version, and request_id, plus optional angle_count, resolution_x, and resolution_y. The description adds no information about any of them, so it fails to compensate for the coverage 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?

States a specific verb (render) and resource (review artifact) and adds a scope hint (new version, approval gate). However, 'review artifact' and 'explicit approval gate' are jargon that don't clearly tell an agent how this differs from sibling render tools like render_shot_preview or render_shot_final, so purpose is only partly distinctive.

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 when-to-use guidance, no prerequisites, and no named alternative. The phrase 'for an explicit approval gate' hints at context but doesn't tell an agent when to pick this over promote_version, compare_asset_versions, or the shot render tools.

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