Get top anime

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

The description details fallback behavior when Tenrai is unavailable, including how type/filter are merged, rating is ignored, and certain fields come back empty. Annotations only indicate readOnlyHint and openWorldHint, so the description adds critical behavioral context beyond the structured data.

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 relatively long but every sentence serves a purpose. It front-loads the main functionality and fallback details. Could be slightly more polished, but there is no extraneous 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?

The description covers when to use the tool, sibling alternatives, parameter interactions, and fallback behavior. Since an output schema exists, return values are not needed. The tool is complex with a fallback mechanism, and the description handles it comprehensively.

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 good descriptions. The description adds value by explaining how parameters behave during the fallback scenario (e.g., rating ignored, sfw_strict degrades), which the schema alone does not convey. This extra context earns a score above the baseline 3.

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 retrieves anime ranked by all-time score/popularity, not tied to any season. It distinguishes itself from siblings like get_seasonal_anime and get_upcoming_season by explaining when to use those alternatives instead.

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 provides usage boundaries: for a specific season's lineup, use get_seasonal_anime or get_upcoming_season. It also explains the fallback behavior and how parameters behave differently when Tenrai is unavailable, guiding the agent on when this tool is appropriate.

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