anilist_compat_card

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

Annotations already indicate read-only and non-destructive behavior. The description adds that the tool returns a PNG image, offering behavioral context beyond annotations. It does not cover potential limitations, but the annotation coverage is high, so the description provides useful addition.

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 sentences, front-loaded with the action and output, no unnecessary words. Every sentence adds value.

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?

The description explains the return value (PNG image with specific content), which is sufficient given no output schema. It covers the main use case and input constraints. Missing details like image format details or user existence requirements are minor given openWorldHint.

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%, with clear descriptions for each parameter. The description does not add detailed parameter semantics beyond stating the output content (genre comparison, etc.), which indirectly relates to the 'type' parameter. Baseline of 3 is appropriate as schema already does the heavy lifting.

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 clearly states the tool generates a shareable compatibility card image comparing two AniList users, specifying the output format (PNG) and content (compatibility %, genre comparison, etc.). It distinguishes itself from siblings like anilist_compare by emphasizing a visual card output.

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?

The description explicitly says 'Use when someone wants a visual comparison of taste,' providing a clear use case. It does not mention alternatives or when not to use, but the context of sibling tools implies text-based comparisons are elsewhere.

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