jikan_search_manga

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 covered upstream. The description adds nothing beyond restating the API source: no note on pagination, result caps, rate limits, or what a search returns. 'via Jikan API' is the only added context.

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 naming verb, resource and backend, with no filler. It is efficient but so terse that the brevity comes at the cost of coverage rather than trimming redundancy.

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 3-parameter, no-output-schema tool, the description should at minimum explain what the optional page/limit do and roughly what comes back. None of that is present, so an agent cannot call it confidently beyond the trivial query case.

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 carries the full burden for three parameters. It implies only that 'query' is a search term; 'page' and 'limit' are never mentioned, leaving the agent to guess whether they are 1-based, capped, or honored at all.

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 gives a specific verb and resource ('Search manga') plus the data source ('on MyAnimeList via Jikan API'), which is enough to separate it from data-fetch siblings like jikan_get_anime. It does not explicitly name which sibling to prefer, so it stops short of a 5.

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 when-to-use statement, no contrast with jikan_get_anime or jikan_top_anime, and no mention of when a keyword search is inappropriate (e.g. fetching a known ID). The agent must infer that this is the lookup-by-title entry point from the verb alone.

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