Delete Deck

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

Discloses deletion of nested decks and cards, adding value beyond the name. However, lacks details on reversibility, permissions, or error conditions.

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?

Single sentence, efficient and to the point. Not overly verbose, but could benefit from structured formatting.

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-param deletion tool with no annotations or output schema, description covers primary scope. Missing error scenarios (e.g., non-existent deck).

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 has no descriptions (0% coverage). Description only mentions deck_name in context but offers no additional meaning on format, constraints, or validation.

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 action 'Delete', resource 'deck', and scope 'nested decks, and all their cards'. Clearly distinguishes from sibling like delete_cards.

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?

Implied usage for deleting a deck and its contents, but no explicit when-to-use or when-not, nor comparisons with alternatives.

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