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

With no annotations, the description carries the full burden and does so well: it discloses that avatarUrl is auto-attached as the img2img reference, that Firestore is the backing store, that the user maintains avatars via aige.ws, and that avatarCount 0 degrades to text-to-image. It omits ordering, default page size, and any auth/scope notes.

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?

Purpose and field list are front-loaded, followed by a clearly labeled mechanism section and a trigger list. It is longer than most list tools need, but the img2img explanation genuinely earns its space; the typographic styling is slightly noisy.

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, and the description compensates by documenting every returned field and the meaning of activeCharacterId. The one real gap is the undocumented `limit` input, which leaves an agent guessing about pagination behavior.

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?

The single parameter `limit` has 0% schema description coverage and the description never mentions it, its default, or its 1-200 range. All of the prose is about return fields, leaving the only input completely undocumented.

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 ('List the user's saved AIGE characters') and enumerates the returned fields, so the agent knows exactly what comes back. It does not differentiate itself from the similarly named sibling antix_list_character_gallery, which is the one plausible source of confusion.

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 four concrete invocation triggers: user names a character, asks 'what characters do I have', wants to verify which avatar will be used for img2img, or is about to generate an image of a specific person/face. No when-not conditions or named alternative tools are given, so it stops short of a 5.

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