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

Goes well beyond the destructiveHint=true / idempotentHint=false annotations: names the exact storage path overwritten (users/<uid>/characters/<characterId>/avatar.jpg), states the previous avatar is returned but not preserved, and notes the change is immediately visible on the AIGE web page. It also discloses the client-side limitation that motivates the design.

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?

Front-loads purpose and usage examples, then uses bold-labelled Inputs/Side effects/Returns sections that scan well. It is longer than strictly necessary — the 'Why this matters' client-limitation discussion is useful but the longest single block, and a little of it could be trimmed without losing agent-relevant information.

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?

No output schema exists, but the description enumerates the return fields (characterId, characterName, avatarUrl, previousAvatarUrl, characterPageUrl). Combined with the documented side effects and the two documented params, an agent has everything needed to call this correctly and report the result.

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 0% and the schema provides no descriptions, so the description must carry the load — and it does. It documents both parameters: characterId sourced from antix_list_characters, and image accepting either an HTTPS URL (with the recommended acquisition path) or a base64 data URL.

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 and resource ('Change the saved AIGE character's avatar') and immediately defines what an avatar means operationally — the img2img reference auto-attached when the characterId is passed to antix_generate_image. That definition cleanly separates it from antix_create_character, antix_add_to_character_gallery, and antix_generate_image in the sibling list.

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?

Gives explicit triggering conditions with three natural-language user utterances ('use this image as Aurora's new face going forward', etc.) and explains the correct alternative workflow when chat bytes aren't forwarded — upload to aige.ws/r or supply any public URL, then call this tool. The when-to-use boundary against per-generation image passing is stated outright.

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