delete_cards

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

Beyond the destructiveHint annotation, the description discloses critical safety behavior: a 30-second user confirmation window, the requirement that the agent never approves the dialog, mandatory verified backup, abort conditions for failure or changed targets, and the side effect of removing an orphaned note when the last card is deleted.

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 front-loaded with the main action, then lists critical constraints in compact sentences. Every sentence carries operational or safety value with no wasted wording.

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?

Given rich annotations (destructive, idempotent, not read-only) and an output schema, the description supplies the missing human-in-the-loop, backup, abort, and cascade-delete behavior. It gives an agent enough information to invoke the tool safely and correctly.

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 only parameter is preview_id, and the description ties it implicitly to a prior card preview. However, with 0% schema description coverage, it does not explain the expected format, source, or lifecycle of preview_id, leaving the agent to infer it.

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 states a specific verb and resource: request deletion of previewed cards. It clearly distinguishes this from siblings like preview_delete_cards by noting that this is the actual deletion request stage and that cards are already previewed.

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?

It gives clear operational context: the user must click Yes within 30 seconds, the agent must never approve the dialog, and a verified recovery backup is mandatory. It implies the prerequisite preview step but does not explicitly name preview_delete_cards as the required alternative.

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