manga_title_characters

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

With no annotations present, the description carries the behavioral disclosure burden. It transparently discloses pagination, the 404 failure mode for anime ids, the credential-free access model, and the fields returned. It does not describe pagination response metadata or behavior for entirely invalid ids, but the key operational traits are covered.

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?

Three sentences with no filler. The core operation is front-loaded in the first sentence, the critical edge case and sibling routing come second, and the access model is tersely stated last. Every sentence contributes actionable 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?

There is no output schema, but the description lists the concrete return fields and notes pagination, which is sufficient for an agent to understand the tool's result. The 404 id-space warning and credential-free note round out operational context. A small gap remains around the exact shape of pagination metadata, but this is minor given the schema already documents page and per_page.

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 coverage is 100% for the three parameters, which sets a baseline of 3. The description adds meaningful extra context for the critical 'id' parameter by explaining the shared AniList id space and why manga ids behave differently from anime ids. It also reinforces pagination semantics for page and per_page, exceeding the baseline.

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 uses a specific verb and resource: 'List a manga's characters.' It enumerates the returned fields (character name, native name, billed role, image, favourites) and explicitly distinguishes itself from the anime equivalent, which is a sibling tool. An agent can immediately tell what this tool does and how it differs from anime_title_characters.

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 explicit routing guidance: the AniList id space is shared but non-overlapping, so an anime id returns 404, and the agent is directed to use GET /anime/title/{id}/characters for those cases. It also notes this is credential-free public data, clarifying the access context. This is strong when-to-use vs alternative guidance.

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