jikan_search_anime

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only the provenance ('via Jikan API'); it says nothing about page size limits, pagination depth, or the rate limiting Jikan is known for.

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?

A single front-loaded sentence with zero filler, so nothing needs trimming. But the brevity comes from omission rather than economy; the one sentence does not earn much because it carries almost no decision-relevant content.

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?

This is a six-parameter search tool with no output schema, so the description should at least indicate what comes back and how paging behaves. Instead it stops at the API name, leaving result shape, page-size behavior, and limit interaction unexplained.

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?

At 67% schema coverage, four of six parameters (type, status, order_by, limit) are documented in the schema while query and page are left bare. The description adds no meaning to any parameter — no search-syntax hints for query, no default for page — so it fails to compensate for the gap.

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?

States a specific verb (search) and resource (anime) plus the data source (MyAnimeList via Jikan), which distinguishes it implicitly from jikan_get_anime (single lookup) and jikan_top_anime (ranked list). It never names those siblings, so the differentiation is inferential rather than explicit.

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?

There is no guidance on when to reach for this versus jikan_get_anime, jikan_top_anime, or jikan_search_manga. The agent must infer from the name alone that this is the keyword-search entry point, and nothing explains prerequisites or result expectations.

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