Get my manga list

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

ReadOnlyHint and openWorldHint are already present, and the description adds meaningful context beyond them by stating that the tool requires a MyAnimeList login and operates on the authenticated user's own data. This helps an agent understand that authentication state and identity are relevant.

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 a single focused sentence that front-loads the key action and resource, then adds the necessary login constraint. No filler or redundant restatement exists.

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?

Given a complete input schema, an output schema, and annotations, the description provides enough context for a safe read-only tool. It could be slightly stronger by naming the closest sibling or confirming this is not the anime-list variant, but nothing critical is missing.

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 100%, so the parameters are already well documented. The description does not repeat or extend parameter semantics, which is acceptable given the schema handles the parameter burden.

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 clearly states the verb ('Get'), the resource ('authenticated user's own manga list'), and the scope ('own'). It is distinct from general manga lookup tools like get_manga, though it does not explicitly distinguish itself from its closest sibling get_my_anime_list.

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 intended use case is implied: use this when the agent needs the current user's own manga list. It also notes the prerequisite of a MyAnimeList login, but it does not explicitly say when to prefer this tool over alternatives such as get_my_anime_list or search_manga.

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