delete_deck

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

Discloses irreversibility and the behavior of the 'cards_too' parameter (deleting cards vs moving to Default). With no annotations, this adds necessary behavioral context for a destructive action.

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?

Three sentences, no wasted words. The core action is front-loaded, and additional details are given succinctly.

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?

Covers all parameters and key behavior. With an output schema present, return info is not needed. Could mention that the deck must exist, but that's implied.

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 0%, but the description fully explains the 'cards_too' parameter's effect, including default behavior, which is absent from the schema. 'name' parameter is self-explanatory.

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 'Delete a deck' with specific verb and resource. The description further distinguishes this from sibling tools like 'delete_notes' by focusing on decks.

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?

Implies usage for deleting decks but does not explicitly state when-to-use versus alternatives like 'delete_notes' or 'create_deck'. No exclusions provided.

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