Log in to AniList

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

Discloses that the tool returns an authorization URL, explains automatic vs manual redirect completion, and does not contradict annotations (readOnlyHint=false, openWorldHint=true).

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?

Concise, front-loaded purpose, logically structured with prerequisites, action, and special case. No wasted words.

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?

Covers all needed information for a login tool: prerequisites, expected output, completion steps. Output schema exists but description already explains return value.

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?

No parameters in input schema; description adds no parameter details. Baseline for 0 parameters is 4. Schema coverage is 100% but irrelevant.

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 tool authorizes personal-list and social tools with AniList account, distinguishing it from sibling tools that use the API after authentication.

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?

Provides prerequisites (register app, set env vars) and steps (open URL, approve, and handling redirects). Mentions alternative tool submit_anilist_redirect for remote setups.

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