Remove anime from my list

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

The description adds significant behavioral details beyond annotations: it reveals that the API always returns `deleted: true` even if the anime was never on the list, and warns about the interpretation of success. This complements the destructiveHint and idempotentHint annotations, providing a nuanced understanding of the tool's behavior.

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 concise with three sentences, each serving a distinct purpose: stating the action, explaining the response caveat, and specifying authentication. It is front-loaded with the purpose and contains no unnecessary 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?

For a simple tool with one parameter, rich annotations, and an output schema, the description is fully complete. It covers purpose, behavioral edge cases, authentication, and cross-references the appropriate sibling tool (get_my_anime_list) for verification.

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?

With only one parameter (anime_id) and 100% schema coverage, the baseline is 3. The description adds no extra semantic detail about the parameter beyond what the schema already provides (numeric ID with constraints).

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's action: 'Remove an anime entry from the authenticated user's list.' It uses a specific verb (remove) and resource (anime entry from list), distinguishing it from sibling tools like get_my_anime_list (read) and update_my_anime_status (update).

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 provides explicit guidance: it notes the action is irreversible, advises checking get_my_anime_list first if confirmation of existence is needed, and clarifies that a successful response does not guarantee prior existence. It also states the authentication requirement, giving clear context for when to use the tool.

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