Delete My Manga Entry

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

The description details the destructive effects (deletes score, progress, dates, tags) and confirms permanence, which goes beyond the annotations (destructiveHint: true). It also discloses idempotent behavior and error handling (404 for unknown id), adding valuable behavioral context.

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 concise, with only two sentences. The first sentence front-loads the main action, and the second provides critical behavioral details. No redundant or 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?

For a simple delete operation with one parameter and an output schema, the description covers the key aspects: what is removed, permanence, idempotency, and error behavior. It could be slightly improved by explicitly mentioning authentication requirement, but the tool name and context imply it.

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?

With 100% schema coverage, the schema already describes 'manga_id' as 'MAL manga id'. The description does not add further semantic meaning to the parameter beyond the context of the delete action, so it meets the baseline.

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 ('PERMANENTLY remove a manga') and the resource ('from the authenticated user's list'). It directly distinguishes from sibling tools like 'update_my_manga_entry' (update vs delete) and 'delete_my_anime_entry' (manga vs anime), leaving no ambiguity.

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 implies usage for removing a manga entry and warns about permanence. It does not explicitly mention when not to use it or direct to a sibling tool like 'delete_my_anime_entry', but the context of siblings and clear action provides sufficient guidance.

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