Update my anime status

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

Annotations indicate write, idempotent, and non-destructive behavior, which the description matches. It adds context about the upsert nature and the requirement for additional fields. The description does not contradict annotations and provides behavioral clarity beyond structured fields.

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?

Two sentences, each earning its place. The first outlines the action and fields; the second gives a crucial usage constraint. 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?

With 8 parameters and no output schema, the description covers the core upsert behavior and required fields. It could mention return values or error conditions, but the current detail is sufficient for a typical update tool.

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%, so the baseline is 3. The description adds meaning by stating the requirement to provide at least one field beyond anime_id, which is not in the schema. This extra constraint adds value for parameter selection.

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 verb (add/update) and resource (anime on authenticated user's list). It differentiates from siblings like get_my_anime_list and delete_my_anime_list_item by specifying upsert behavior and focusing on status updates.

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 explicitly requires at least one field besides anime_id, which guides parameter usage. It also implies creation if absent, indicating when to use this tool. However, it does not explicitly exclude scenarios or mention alternatives like the manga counterpart.

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