Update my manga status

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

Discloses upsert behavior ('Creates the entry if absent') and required action. Annotations indicate write, idempotent, and non-destructive, which the description aligns with. Does not mention authentication, but that's implicit.

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 concise sentences, front-loaded with purpose and key constraint. No wasted 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?

Adequately covers core behavior for a 7-parameter tool with no output schema. Could mention return values or errors, but the description is sufficient for selection and basic usage.

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 good descriptions in the schema itself. The description adds only a usage constraint ('Provide at least one field besides manga_id'), not additional parameter meaning. Baseline 3 is appropriate.

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?

Clearly states it adds or updates a manga on the user's list, specifying key fields (status, score, chapters/volumes). Distinguishes from sibling tools like delete_my_manga_list_item or get_my_manga_list.

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?

Provides a clear usage guideline: 'Provide at least one field besides manga_id.' Does not explicitly state when not to use or mention alternatives, but context with siblings implies proper use for modifying user list.

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