apple_reminders_delete_list

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description still adds real value beyond them by disclosing the cascade behavior (all contained reminders are deleted too) and that the change may propagate to iCloud, neither of which is derivable from the 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?

Two short sentences, zero waste, with the destructive scope front-loaded ahead of the secondary sync caveat.

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 delete with no output schema, the description covers what gets removed (the list plus its reminders), that it is destructive, and that it may sync to iCloud. It leaves open how the target list is identified and whether deletion is recoverable, which are minor but non-zero gaps.

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% for the single required 'id' parameter, and the description says nothing about it — the agent cannot tell whether to pass a list name, a UUID from apple_reminders_list_lists, or another identifier. With low coverage the description is expected to compensate 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?

The description names a specific verb (Delete) and resource (a Reminders list), and explicitly states the cascade scope — 'and its reminders' — which separates it from the sibling apple_reminders_delete that removes a single reminder. It does not, however, explicitly name or contrast against that sibling, so it stops short of a 5.

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 when-to-use guidance, no stated prerequisite (e.g. confirmation, permissions), and no mention of the alternative tools for removing reminders versus removing an entire list. 'Destructive; may sync to iCloud' is a warning, not routing guidance.

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