add_flashcard_deck

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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly discloses the non-obvious side effect of creating a flashcards section if the site lacks one, and it explains the SM-2 spaced-repetition review behavior. It does not mention permissions or idempotency, but the main side effects are usefully surfaced.

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?

The description is three short sentences, front-loaded with the main purpose. Every sentence adds meaningful context: the action, the section-creation side effect, and the review behavior. There is no redundant or filler content.

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?

Given the nested deck parameter, optional section_id, and the nearby add_flashcards sibling, the description is too sparse for reliable invocation. An agent can understand the tool's high-level purpose but cannot confidently determine how slug, section_id, and deck fields should be supplied. The output schema may help with return shape but does not resolve these parameter-level 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?

Schema description coverage is only 33%, and the description does not compensate: it never explains slug, section_id, or how the deck object should be structured. The schema's deck description lists fields, but slug and section_id semantics are completely opaque. This leaves significant ambiguity for invoking the tool correctly.

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?

The description clearly states the resource and action: 'Add a new flashcard deck to a site.' It also adds a useful non-obvious detail about creating a flashcards section if none exists. It does not explicitly contrast with the sibling tool add_flashcards, though the deck-versus-cards distinction is inferable.

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?

Usage is implied: an agent should use this when adding a deck to a site. However, there is no explicit guidance about when to prefer this over add_flashcards or how it relates to removing or updating decks. The only contextual hint is the auto-creation of a flashcards section.

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