Update my manga status

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

Adds key behavior beyond annotations: 'Creates the entry if absent' (upsert behavior). Annotations already indicate it's write, non-destructive, idempotent, and open-world. No contradictions.

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. First sentence states primary action and scope. Second adds a critical 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 tool behavior (upsert, required field) and context (authenticated user). No output schema, but description suffices for a straightforward mutation tool. Could mention allowed status values but schema handles that.

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 covers all 11 parameters with descriptions (100% coverage), so baseline is 3. Description adds the constraint 'Provide at least one field besides manga_id,' which is helpful but not a deep semantic addition.

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 adds or updates a manga on the user's list, specifying the fields (status, score, chapters/volumes read). It distinguishes from siblings like delete_my_manga_list_item (delete) and get_my_manga_list (read), and from update_my_anime_status by focusing on manga.

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 hint: 'Provide at least one field besides manga_id.' Implicitly distinguishes from siblings (delete, get) but does not explicitly list alternatives or conditions to avoid.

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