Log in to MyAnimeList

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

Discloses that it returns an authorization URL, requires user interaction, and explains automatic vs manual redirect. Adds behavioral context beyond annotations (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?

Efficient, front-loaded with purpose, then prerequisite, steps, and edge cases. No wasted sentences.

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?

Complete for an auth tool: explains output (URL), next steps, and different environments. No output schema needed.

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, so schema coverage is 100%. Description appropriately says nothing about parameters as none exist.

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 it authorizes personal-list tools via one-time login. It distinguishes from sibling tools that are read-only or update operations.

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?

Explicitly states it's a prerequisite for personal-list tools, provides step-by-step setup (register app, set env var), and explains when to use submit_mal_redirect. Covers local vs remote browser scenarios.

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