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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and data-source scope are covered. The description usefully adds result ordering and the fact that recommendations can span media types, but says nothing about pagination limits or result volume beyond what the schema implies.

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?

Two short sentences, the primary output semantics front-loaded, zero filler. Nothing could be removed without losing 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?

With a 3-param schema at full coverage and an output schema present, the description only needs to frame the result set, which it does. The one gap is that it never tells the agent where the required manga id should come from.

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%, so id, page, and per_page are already documented with defaults and clamping. The description adds no parameter detail; note the schema labels id as an 'AniList anime id' despite this being a manga tool, and the description does not clarify that ambiguity.

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 resource (titles recommended alongside a manga) and the ordering rule (most-recommended first), which is more than the name alone conveys. It does not, however, distinguish itself from nearby siblings such as manga_title or anime_title_recommendations, so an agent must infer the boundary.

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 gives no when-to-use guidance, no prerequisites (e.g. that the id must come from manga_search or manga_title), and no mention of alternatives. The 'cross media types' note is a property of results, not a usage rule.

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