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

With no annotations, the description carries the full burden and does well: it discloses the cost ('Costs one image') and the destructive side effect that the new picture 'replaces the old one', which an agent needs before overwriting user work. It stops short of stating whether the old image is recoverable or what happens on failure, so a four rather than a five.

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?

Two compact sentences, front-loaded with the action and its core constraint, followed by cost and replacement behavior. Every clause carries information an agent needs; nothing is filler.

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 two-parameter mutation tool with no annotations and no output schema, the description covers the essentials: what it edits, the single-change rule, the credit cost, and that the old image is replaced. It lacks only explicit sibling routing and failure-mode behavior to be fully 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 both parameters are already documented, so the schema does the heavy lifting. The description adds meaning by illustrating the 'change' parameter with natural-language examples ('give him a blue tunic', 'make her older') and by emphasizing 'ONE change', which constrains how the free-text field should be filled.

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 gives a specific verb and resource ('Regenerate one of the user's 3D characters') plus the key constraint of a single change, so the action is unambiguous. It does not distinguish itself from close siblings such as change_character, manage_3d_character, or create_3d_character, so an agent must infer the 3D-specific boundary.

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?

Usage is implied rather than stated: 'keeping everything else the same' signals this is for small edits to an existing character, and the three quoted examples clarify acceptable change requests. There is no explicit when-not guidance or named alternative (e.g. creating a new character vs editing) to route the agent among siblings.

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