get_anime_ranking

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

With no annotations, the description should disclose behavioral traits like read-only nature, rate limits, or authentication needs. It only explains input parameters but omits any operational context beyond the obvious 'fetch' action.

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 structured with clear sections for each parameter. However, it is somewhat verbose, resembling a docstring. A more streamlined version could convey the same information more efficiently.

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?

Given no output schema, the description covers the input parameters comprehensively. However, it does not explain the output format or pagination behavior beyond offset/limit, leaving some gaps in completeness for a fetch operation.

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 0%, so the description fully compensates by listing each parameter with valid options (ranking_type enum), defaults and maximum for limit, and offset purpose. This adds meaning beyond the bare schema types.

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 'Fetches anime rankings from MyAnimeList' with a specific verb and resource. It distinguishes from sibling 'get_manga_ranking' by specifying anime. Additional context on ranking types further clarifies purpose.

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?

No guidance on when to use this tool over alternatives like 'get_seasonal_anime' or 'get_suggested_anime'. The description lacks context for selection criteria, leaving the agent to infer usage from parameter differences alone.

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