APIbase

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

With no annotations provided, the description carries the full burden. It successfully discloses the data source ('MyAnimeList via Jikan') and enumerates returned fields (synopsis, chapters, volumes, etc.), but lacks information on error handling, rate limits, or behavior when an invalid ID is provided.

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?

Single, dense sentence that front-loads the action ('Get full manga details'), specifies the key parameter ('by MAL ID'), lists return fields using an em-dash, and attributes the data source parenthetically. Zero waste and appropriately sized for the tool's simplicity.

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?

For a single-parameter lookup tool without output schema, the description adequately covers the essential contract: input requirement (MAL ID) and output fields. Minor gap in not describing error cases (e.g., invalid ID), but sufficient for the tool's complexity level.

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 schema has 100% description coverage with examples (e.g., '13 for One Piece'), establishing a baseline of 3. The description reinforces the 'MAL ID' requirement but does not add semantic meaning beyond what the schema already provides.

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 specific verb 'Get' with clear resource 'manga details' and distinguishes from anime-focused sibling tools by specifying 'manga' and 'MAL ID'. It clearly differentiates from anime.titles.details by targeting manga specifically.

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 phrase 'by MAL ID' implies this is a lookup tool requiring an identifier, suggesting it should be used when the ID is known. However, it does not explicitly reference sibling search tools (like anime.titles.search) or state when to use search vs. this direct lookup.

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