mdl_watchlist_remove

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds value beyond them by disclosing the authentication requirement ('host-configured MyDramaList authentication') and reinforcing the explicit-user-request guardrail. It stops short of explaining behavior for nonexistent IDs or partial-batch failures.

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 short sentences, front-loaded with the operation and endpoint, then the critical ID caveat, then the auth/guardrail note. No sentence is filler.

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 one-parameter mutation with full annotation coverage and no output schema, the description supplies everything needed to invoke correctly: endpoint, body shape, ID semantics, auth prerequisite, and a usage guardrail.

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 0% schema description coverage the description must carry the load, and it does the most important thing possible: it clarifies that the IDs are title IDs, not list entry IDs, and shows the expected JSON array body shape. That resolves the single ambiguity most likely to cause a wrong call.

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?

States a specific verb and resource (remove watchlist entries) and pins down the exact underlying operation (DELETE /sync/mylist), which cleanly separates it from the sibling mdl_watchlist_add and the read-only mdl_watchlist_fetch variants.

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?

Gives an explicit usage constraint ('use only for an explicit user request'), which is real when-to-use guidance. It does not, however, name the alternative tools (mdl_watchlist_add, mdl_custom_lists_remove_item) or state what to do if the user only implies removal.

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