anilist_list

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

Annotations declare readOnlyHint=true, and the description reinforces this by using 'Get' and listing return fields. No contradictions. It adds context about return fields (title, score, progress, etc.) beyond annotations. No destructive behavior is implied.

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, each packing information: purpose, usage examples, and return details. No filler or redundancy. Front-loaded with the primary action.

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 7 parameters and no output schema, the description adequately explains the return format and usage context. It doesn't detail pagination or authentication, but annotations cover safety. It is sufficiently complete for a list retrieval tool.

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 baseline is 3. The description adds value by summarizing return fields ('Returns entries with title, score, progress, status, updated date, and entry ID'), which is not in the schema. It also mentions custom list support, but schema already covers that. Overall, it goes beyond the schema.

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 'Get a user's anime or manga list, filtered by watching status.' This is a specific verb+resource combination. It differentiates from sibling tools like anilist_add_to_list or anilist_delete_from_list by focusing on retrieval and filtering.

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 explicitly states when to use: 'when the user asks about their list, what they're watching, what they've completed, or what's on their plan-to-watch.' It also mentions custom lists. It does not provide explicit exclusions or alternatives, but the context is clear.

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