swu_export_deck

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

No annotations are present, so the description carries the full burden of disclosing behavioral traits. It does not state whether the operation is read-only, requires authentication, has side effects, or what happens with conflicting inputs (e.g., both decklist and session_id provided). This is a significant gap for a tool that might have hidden constraints.

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 a single, front-loaded sentence with no filler or repetition. It conveys the core purpose and output formats efficiently, earning a perfect score for conciseness.

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?

Despite an output schema, the description lacks critical context about parameter dependencies and combination rules. With four optional parameters and no guidance on how they interact, the tool is under-specified for correct invocation. The description does not cover prerequisites, fallback behavior, or precedence.

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 0%, so the description must compensate, but it only maps 'deck session' and 'decklist' to session_id and decklist. It does not explain format_name (e.g., 'premier') or export_format values beyond the generic 'plain text or JSON', leaving the agent guessing about parameter defaults and allowed values.

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 uses a specific verb 'export' with a clear resource ('deck session or decklist') and format ('plain text or JSON'). This distinguishes it from sibling tools like swu_upload_deck, swu_validate_deck, and swu_analyze_deck, which have different purposes.

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?

The description implies usage when a deck export is needed but offers no explicit guidance on when to use this tool versus alternatives (e.g., swu_upload_deck for importing). No exclusions or alternative tool mentions are provided, leaving the agent to infer context from the tool name.

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