mdl_custom_lists_delete

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

Annotations already declare destructiveHint=true, openWorldHint=true and non-idempotence, so the safety profile is covered. The description adds meaningful context beyond that: host-configured MyDramaList authentication is required and the call mutates remote data, plus the explicit-request guardrail. It stops short of saying what is destroyed (list plus its items) or whether it is reversible.

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 clauses, front-loaded with the action and followed by auth and safety constraints. Efficient, though the opening 'Custom Lists: delete' is largely redundant with the tool name rather than adding 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 destructive, single-parameter mutation with no output schema and no annotation-level detail about permissions, the description covers auth and user-request guardrails but leaves the parameter meaning and the blast radius of the deletion unexplained. Adequate but with obvious holes.

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?

There is one required parameter (list_id) with 0% schema description coverage, yet the description says nothing about it — not the accepted integer/string forms, not the alphanumeric pattern, not what a valid list id looks like. Since the description must compensate for the complete lack of parameter documentation, this is a clear gap.

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 verb (delete) and a resource (Custom Lists), but functionally restates the tool name rather than explaining what deleting a custom list entails. It does not distinguish this from close siblings like mdl_custom_lists_remove_item or mdl_custom_lists_edit, which an agent could easily confuse with 'delete a 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?

'use only for an explicit user request' gives a real usage constraint, which is more than most siblings offer. However, it provides no guidance against alternatives (e.g., edit vs remove_item vs delete) or any prerequisite flow, so routing between the custom-list mutation tools remains inferential.

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