get my manga list

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

The annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral context by saying it returns one page and that callers should follow hasNextPage, and it lists returned fields such as chapter/volume progress, scores, and genres. It does not cover auth or rate limits, but the annotation coverage lowers the burden.

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 concise sentences with no wasted language. The core purpose is front-loaded, and the pagination instruction follows immediately.

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 helpfully names returned fields and pagination behavior. However, it leaves the undocumented status and per_page parameters unexplained, so it is only minimally complete for a tool with three parameters at 0% schema coverage.

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 0%, so the description must compensate, but it only hints at the page parameter through 'one page' and 'hasNextPage.' It does not explain the status filter or its enum values, nor per_page, its default, or its maximum.

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 states a specific verb and resource: reading one page of the owner's manga library, including progress, scores, and genres. This clearly distinguishes it from search_manga and from get_my_anime_list, though it does not explicitly name any sibling tool.

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?

Usage is implied by 'owner manga library' and the pagination instruction 'Follow hasNextPage for the complete library.' However, there is no explicit guidance on when to choose this over search_manga or get_manga_details, nor any stated exclusions.

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