Get anime news

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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds critical behavioral context about the sfw parameter, revealing that setting it to true 'returns an empty list entirely for an NSFW-rated anime (verified live) rather than filtering individual articles', which goes beyond the schema description.

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?

The description is front-loaded with the main purpose and is generally concise. However, the explanation of sfw behavior is somewhat lengthy and could be slightly more structured. Still, it avoids unnecessary verbiage.

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 covers the tool's purpose, usage context, parameter behavior, and differentiation from siblings. Since an output schema exists, return value details are not needed. It is sufficiently complete for an agent to decide when and how to call this tool.

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%, but the description enriches understanding by explaining the nuanced difference between sfw and sfw_strict, including that sfw alone still allows Ecchi-tagged shows and that sfw_strict excludes them. It also notes that sfw returns empty list for NSFW anime, which is not stated in the schema.

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?

Description clearly states 'List recent news articles about an anime (by mal_id)' and specifies the fields returned: headline, date, author, excerpt. It distinguishes from the sibling tool get_news by noting it is for news tied to a specific anime, while get_news is for a site-wide feed.

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?

Explicitly says 'Useful for "what's new / any announcements" questions' and advises 'Get the mal_id from search_anime'. It also provides an alternative: 'Use get_news instead for a site-wide feed not tied to one anime'.

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