Get manga recommendations

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

Beyond annotations (readOnlyHint, openWorldHint), the description adds valuable traits: no pagination, top 25 cap, and a transparent fallback retry mechanism via the official API if Jikan is unavailable, noting potential differences in ordering/counts. This fully discloses behavior.

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 brief (3 sentences) and efficiently front-loaded: core purpose first, usage guidelines second, behavioral detail third. No extraneous words; every sentence earns its place.

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?

With an output schema present, the description covers all essential aspects: operation, input source, alternative tool, constraints, and fallback behavior. It is fully sufficient for an agent to correctly select and invoke the 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% (parameter 'id' described as 'MyAnimeList numeric ID'). The description adds context by stating 'Get the mal_id from search_manga,' which provides sourcing guidance beyond the schema, justifying a score above 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 explicitly states 'Get community recommendations for manga similar to the given mal_id, ordered by votes and capped at the top 25 (no pagination).' It clearly identifies the verb, resource, and constraints, and distinguishes from siblings like get_top_manga by specifying this is for similar manga tied to a specific ID.

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 provides an explicit alternative: 'Use get_top_manga instead for a global popularity/score ranking not tied to one title.' It also advises getting the mal_id from search_manga, offering clear when-to-use and when-not-to-use guidance.

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