anilist_favourite

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

The description explains the toggle behavior (calling again removes) and authentication requirement, which adds value beyond the annotations. It aligns with destructiveHint and idempotentHint, and there is no contradiction.

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 two sentences, front-loaded with the action, and contains no extraneous information. Every sentence is useful.

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?

The description covers the core functionality, toggle behavior, and authentication. There is no output schema, so the return value is not explained, but for a toggle operation this is acceptable.

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 input schema already fully describes the two parameters with enums and integer constraints. The description mentions the entity types but does not add new semantic meaning 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 the action ('Toggle favourite') and the resource (anime, manga, character, staff, or studio). It distinguishes itself by focusing on the toggle behavior, which is different from other tools like anilist_react or anilist_rate.

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 explains the toggle behavior and that it requires ANILIST_TOKEN, which are important usage details. However, it does not explicitly compare with sibling tools or provide when-not-to-use conditions.

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