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

Annotations only cover the generic flag profile (not read-only, not destructive, not idempotent, closed-world). The description goes well beyond them by disclosing the ~30-60s latency, the ~2 Metodic credit cost, and the side effect that the deck is also persisted to the user's decks. Those are exactly the operational facts an agent needs before invoking a slow, credit-consuming tool.

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 purpose and the visual result are front-loaded, and the operational facts (one call, latency, cost) are packed into a short trailing sentence. It is dense without being bloated, though the parenthetical card-appearance detail is slightly decorative for an agent deciding whether to call the tool.

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 no output schema, the description correctly compensates by describing what the user sees (paper cards in chat, flip interaction) and what is persisted. Cost, latency, and single-call behavior round it out; only failure modes (e.g. insufficient credits) are unaddressed.

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 100%, so both count and session_id are already documented in the schema, and the description adds essentially no syntax or format detail beyond them. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

Names a specific verb (generate) and a specific resource (a METHOD CARD DECK for a session), and describes the artifact concretely: post-it colours, icon on the front, steps and tip on the back. It is clearly distinguishable from sibling generators like generate_slides or generate_worksheet by the card-deck output, though it never explicitly contrasts itself with them.

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 by 'for the session' and by naming the required session_id, so an agent can infer this is a per-session generation step. However, there is no explicit when-to-use vs. when-not, and no guidance on choosing this over generate_handout, generate_worksheet, or other sibling generators that also produce session artifacts.

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