delete_deck

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

Discloses that the action is permanent and deletes all associated cards. With no annotations provided, this covers the essential destructive behavior. Could add more detail on atomicity or rollback, but sufficient for a simple operation.

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, no wasted words. Front-loaded with the primary action. Every sentence adds value: first states action, second states permanence and requirement.

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 single-parameter destructive tool with no output schema, the description fully covers what the agent needs: what it does, side effects, and a prerequisite. No 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?

The schema already describes the deckId parameter with source recommendations. The description adds no further parameter details, so baseline 3 is appropriate given 100% 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?

Clearly states the tool deletes a deck and all its cards, distinguishing it from update_deck and create_deck. The verb 'delete' and resource 'deck' are specific and unambiguous.

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?

Explicitly says the deletion is permanent, warning against accidental use. Mentions the API key requirement. However, it does not explicitly contrast with sibling tools like delete_transaction, though the name and context suffice.

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