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

Annotations (readOnlyHint=false, destructiveHint=false) already signal this is a non-destructive write. The description adds meaningful side-effect disclosure: the deck is created if it doesn't exist, which is not obvious from annotations. It also sets expectations for card content (single clear question, concise answer) that affects study session behavior. No contradiction with annotations.

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 with no filler. The core purpose is first, followed by a batching recommendation and card-format guidance. Every sentence earns its place, and the description is appropriately short for the tool's complexity.

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?

With an output schema present, the return format is covered elsewhere. The description covers the tool's behavior (creating cards, auto-creating deck), usage pattern (batch), and input formatting (front/back quality). Nothing an agent needs to call it correctly is missing.

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 covers the deck parameter and the tags sub-field, but front and back have no schema descriptions. The description directly addresses this gap by specifying what fronts and backs should be ('single clear question' and 'concise answer'), adding semantic meaning beyond the schema. This compensates for the 50% 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?

States the exact action (create flashcards), the target resource (a deck), and a key nuance: the deck is created if missing. This clearly differentiates it from create_deck (which creates only the deck) and from update_card/delete_card. An agent immediately knows what this tool does and how it differs from siblings.

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?

Gives a concrete use case ('turning pasted notes into cards') and advises batching all cards into one call, which is actionable guidance. It does not explicitly name alternatives like create_deck, but the 'created if missing' clause implies you don't need to pre-create the deck. Lacks an explicit 'when not to use' statement, so not a 5.

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