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

With no annotations, the description carries the load and does well: it declares this is a read, discloses the shared bidirectional storage between MCP and the web PromptBar, and explains the side effect that the last image becomes the default img2img reference. It omits any statement about what happens with an empty gallery or auth/permission requirements, which is a minor gap for a read-only tool.

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 the concrete action and the return shape, then adds usage. The 'Why this exists' paragraph is longer than strictly needed for a single-parameter read, but it does carry real behavioral information (gallery reuse, byte-forwarding limitation) rather than pure marketing.

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 enumerating the returned fields (characterId, characterName, images, count, characterPageUrl). Combined with the usage triggers, an agent has nearly everything needed; only the provenance of characterId is missing.

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?

One parameter at 0% schema description coverage, so the description must compensate. It conveys that the parameter identifies a character and that characterId/characterName come back in the response, but never says where to obtain a characterId (e.g., via antix_list_characters) or whether it accepts a name — leaving the only input underspecified.

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: read the user's saved 'Upload' gallery for a character, returning reference image URLs. It implicitly separates itself from antix_add_to_character_gallery (write side) and antix_list_characters (enumerating characters), so an agent can route without opening a schema.

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 triggers ('what references do I have for X', picking an existing reference, checking before adding to avoid duplicates) and names the downstream consumer, antix_generate_image, describing the auto-attach fallback. Alternatives and their selection conditions are spelled out rather than inferred.

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