Remove an entry from your AniList list

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds that the operation cannot be undone, providing nuance beyond annotations. However, it does not detail other behavioral aspects like side effects or error states.

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 a single, focused sentence that front-loads the authentication requirement and concisely conveys the action, resource identification, and irreversibility. No extraneous information.

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 the tool's simplicity (one parameter) and the presence of an output schema, the description covers the essential aspects: authentication, how to obtain the ID, and the irreversible nature. It lacks detail on success/error responses but that is likely handled by the output schema.

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% for the single parameter listEntryId, and the description reiterates the same information (specifying it is the list entry ID, not the media ID). The description adds no new 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 (delete/remove) and the specific resource (AniList list entry), distinguishes it from media ID, and tells how to obtain the correct ID from get_user_list. This differentiates it from sibling tools like update_list_entry or add_list_entry.

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 specifies the prerequisite (requires login) and the prerequisite tool (get_user_list) to obtain the list entry ID. It also states the operation is irreversible. However, it does not explicitly mention when not to use this tool versus alternatives like delete_thread_comment.

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