anime_title

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

The description notes the tool uses public AniList data and optionally scrapes MAL without credentials, but lacks details on rate limits, error handling, or data freshness.

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 cover the main purpose and extra parameter behavior, though the list of fields could be more structured.

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?

For a single-item retrieval, the description lists all returned fields, but could mention error scenarios or data format details.

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%, and the description adds value beyond the schema for the 'mal' parameter (adds one fetch, omitted if no MAL id).

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 'Get an anime' and lists all returned fields, distinguishing it from sibling tools like anime_title_characters or anime_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?

The description implies usage when you have an AniList id and want detailed info, but does not explicitly mention when to use this tool vs alternatives like anime_search or anime_rankings.

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