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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds genuinely new operational context: the deletion cascades to all items, it is irreversible, it requires explicit confirmation, and writes are never auto-retried — behavior an agent cannot derive from the annotations alone.

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?

Four short sentences, front-loaded with the action and cascade consequence, then the approval gate and retry policy. 'Delete list. Delete a list and all its items.' is mildly redundant but the rest earns its place.

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 two-parameter destructive tool with no output schema, the description covers the essentials an agent needs: what is destroyed, irreversibility, the confirmation gate, and retry semantics. Only the relationship to sibling delete/patch tools on the same resource is left unstated.

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 coverage is 50%: confirmed already carries a description ('Set true only after the user approves this change or credit use') and the description reinforces that gating requirement. However, the nested path/list_id structure is not elaborated in the description, so it adds only marginal meaning over the schema. Baseline 3 is appropriate.

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 ('Delete list') and immediately adds scope that matters: it deletes the list AND all its items. The cascade wording implicitly separates it from dealmachine_delete_lists_list_id_items, but the sibling is never named explicitly, so differentiation requires inference.

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 a concrete precondition for invocation: user approval must be obtained and confirmed=true set before the call. It stops short of naming alternatives (e.g., deleting individual items instead of the whole list) or stating when-not-to-use, so it is clear context without exclusions.

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