Delete a card stack

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

Annotations already mark destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds the useful behavioral fact that deletion will be refused until card stacks get their own permission level, which is not captured by any annotation.

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 sentences with zero filler: the purpose is front-loaded, and the second sentence adds an important caveat without repetitive or extraneous explanation.

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 destructive tool with no output schema, this description covers the action, the identifier, and a key failure mode. It doesn't detail what happens to associated cards after deletion, but the destructiveHint annotation supplies the needed safety framing.

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 100% and the schema already describes stackId as 'Id of the stack'. The description adds no additional detail about format, constraints, or valid values, so it meets the baseline for full schema coverage.

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?

Description opens with 'Delete a card stack by id', a specific verb and resource, and clearly differentiates deletion from sibling reset-card-stack, shuffle-card-stack, and other card-stack operations.

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?

The first sentence states the usage action and target precisely. The second adds a concrete precondition (deleting is refused until grant stack permission level), but it doesn't explicitly call out alternatives such as reset-card-stack.

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