Reminders Delete List

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

Annotations already indicate destructiveHint=true, openWorldHint=false, and idempotentHint=false, but the description itself adds no behavioral context. It does not state that deleting a list may cascade to contained reminders, whether deletion is reversible, or any permission requirements. The description contributes nothing beyond the structured annotations.

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 short, but not usefully concise — it is under-specified and repeats the tool name. No information is front-loaded because no functional information exists at all.

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?

Even though the tool has a single parameter and an output schema, this is a destructive operation that gives the agent no indication of what it deletes, what the side effects are, or how to identify the target list. The description is far below minimum viable completeness.

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?

The parameter list_id has no description in the schema, and schema description coverage is 0%. The tool description also never explains what list_id should be, where to obtain it, or how it is used. The description fails to compensate for the lack of parameter documentation.

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 simply restates the tool name — 'reminders_delete_list' — and adds only generic boilerplate about being a delegated Apple domain tool exposed through MCP. It never explicitly says 'deletes a reminder list,' so the agent must infer behavior from the name. This is a tautology rather than a functional explanation.

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?

There is no guidance about when to use this tool instead of related siblings such as reminders_delete_reminder, reminders_create_list, or apple_suggest_reminder_lists. The description provides no selection criteria, prerequisites, or alternatives.

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