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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower. The description still adds real context: the data is credential-free public AniList data, and results are paginated with per_page clamped to 50 — a behavioral constraint an agent needs when sizing requests.

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-loaded with the return payload, then source/auth note, then pagination facts. Efficient, though the parameter restatements duplicate the schema and add length without new 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?

With an output schema present, return values need not be detailed, and the description covers source, pagination, and the id-acquisition path. It is a read-only, open-world query tool, and nothing critical is missing for correct invocation.

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 description coverage is 100%, so page/per_page/id semantics are already documented. The description restates them verbatim (default 1, default 10, clamped to 50) without adding format or interaction details, so the baseline 3 applies.

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?

Specific verb and resource ('Returns community-recommended titles for an anime'), and it states the payload shape (recommendation rating plus full normalized media entry). This clearly separates it from anime_title, anime_title_characters, anime_title_staff, and manga_title_recommendations.

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?

It gives one routing hint, 'Use anime_title to get an anime,' which is genuinely useful since a numeric id is required. However it offers no when-not guidance and never distinguishes itself from the sibling list tools (characters, staff) that also take a title id.

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