manga_title_staff

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

With no annotations provided, the description carries the full burden and delivers: pagination behavior, a distinctive data format detail (volume ranges per credit), a 404 edge case for anime IDs, and an auth statement ('Credential-free public AniList data'). These are substantive behavioral disclosures beyond the bare operation.

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 front-loaded with the core action, then organizes return contents, a differentiating data nuance, error routing, and auth context. Each sentence earns its place, though the middle sentence is slightly dense; it remains efficient and free of fluff.

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 must explain return values, and it does: people, roles, occupations, images, pagination, plus the volume-range nuance. It also covers error behavior and credential requirements, making it fully adequate for correct invocation.

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%, so the baseline is 3. The description reinforces that 'id' must be a manga id (anime ids 404) and confirms pagination via 'paginated,' but it does not add meaningful semantics beyond what the schema already states for page and per_page defaults.

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 opens with a specific verb and resource: 'List a manga's staff credits.' It enumerates the exact contents (author, artist, assistants, translation/lettering credits, role, occupations, image) and explicitly distinguishes itself from anime staff credits, making the tool's scope unambiguous.

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?

Provides explicit when-not-to-use guidance: 'An anime id here returns 404 -- use GET /anime/title/{id}/staff for those.' This directly routes the agent to the correct sibling tool and clarifies the condition, leaving nothing to inference.

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