get manga details

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the description's added value is in disclosing the payload: chapter/volume counts, genres, the caller's existing entry, and community recommendations — the last two hint at user-scoped data and external aggregation. It omits what happens for an unknown/private ID, which matters given the word "verify".

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?

One front-loaded sentence with a semicolon-delimited payload list; every clause carries information an agent can act on, and there is no boilerplate.

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 no output schema, the description is the only signal about return contents and it does list them adequately. However, for an openWorld read that can fail on invalid IDs or touch user-scoped data, it gives no error or auth context, so it is adequate but not complete.

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?

The single parameter has 0% schema description coverage, so the description must carry it, and "AniList manga ID" does constrain the opaque integer to a specific ID namespace. It does not say where to source that ID (search_manga) or that it must be a manga rather than an anime ID, leaving a small but real 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?

Specific verb+resource: it names the AniList manga ID and enumerates what is read (chapter/volume counts, genres, existing entry, recommendations). That separates it from get_anime_details and the list-mutation siblings. It falls short of 5 only because sibling differentiation is implicit rather than stated.

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?

"Verify an AniList manga ID" implies the use case (resolving/validating an ID before calling add_manga_to_list or update_manga_progress), but the agent must infer that. There is no explicit when-to-use, no statement that search_manga should be used first to obtain an ID, and no exclusion of any sibling.

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