Update my anime status

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

Annotations already indicate idempotent, not read-only, not destructive. The description adds useful behavioral details: entry creation if absent, omitted fields left unchanged, and specific authentication methods required (login_mal, tokens). No contradiction with annotations.

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?

Three concise sentences: first states action and scope, second explains behavior for new vs existing entries, third adds constraint and auth requirements. No redundant or filler content; information is front-loaded.

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 complexity (12 parameters, output schema exists), the description covers the essential behavior: add/update, partial updates, required additional field, and authentication. It doesn't discuss error handling, but output schema likely covers return values.

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 coverage is 100% with full parameter descriptions, so baseline is 3. The description adds value by stating the constraint 'Provide at least one field besides anime_id' and grouping fields conceptually (status, score, watched episodes, dates), which is not in 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 'Add or update an anime on the authenticated user's list' with specific fields (status, score, watched episodes, dates). It also distinguishes from sibling tools like update_my_manga_status and delete_my_anime_list_item by focusing on anime list management.

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: 'Provide at least one field besides anime_id' and notes authentication requirements. While it doesn't explicitly state when not to use, the action verb 'update' and mention of 'create if absent' make the usage context clear compared to read/delete siblings.

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