mdl_custom_lists_remove_item

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is known. The description adds non-redundant context: the auth requirement and an explicit caution that it mutates remote MyDramaList data. It stops short of saying whether removal is reversible or what happens if the item isn't present.

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, then auth, then caution. No wasted words, though the leading label style ('Custom Lists: remove item') is slightly redundant with the tool name.

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?

No output schema, so the description needn't explain returns, and annotations plus the auth/destructive notes cover the behavioral essentials. However, for a two-parameter destructive mutation with 0% parameter documentation, the complete absence of parameter guidance leaves a real gap.

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 description coverage is 0% and neither parameter has any prose. The description never clarifies that list_id identifies the target list and item_id the entry to remove, nor does it address the int-or-string anyOf ambiguity. With no schema documentation, the description should have compensated and does not.

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?

Names a specific verb and resource ('Custom Lists: remove item'), which clearly separates it from sibling mutations like mdl_custom_lists_add_item and mdl_custom_lists_sort_item. It is clear but not exceptionally descriptive — it doesn't say what an 'item' is or which list field identifies the target.

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?

Explicitly states the precondition (host-configured MyDramaList authentication) and a usage constraint ('use only for an explicit user request'). This routes the agent away from speculative calls, though it doesn't contrast against add_item/edit as the alternative operation.

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