ygo_generate_tournament_decklist_pdf

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the output is an official Konami KDE Deck Registration Sheet PDF with full category tables and correct Unicode handling, but it does not explain file-writing behavior, overwrite semantics, default output location, error cases, or whether deck legality is validated before generation.

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 two concise sentences, front-loaded with the core transformation and followed by two relevant capabilities. There is no unnecessary wording or structural clutter.

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 an 11-parameter generation tool with no annotations and no output schema, the description covers the essential purpose, input varieties, output artifact, and Unicode handling. The remaining parameter details are fully covered by the schema, though file-output behavior could be clearer.

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 the input schema already documents all 11 parameters. The description reinforces accepted deck input formats but adds little meaning beyond the schema for format, country, event metadata, duelist names, cardGameId, or outputPath, so the baseline of 3 is appropriate.

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 states a specific verb and output resource: it turns deck inputs (YDK, YDKE, .ydk files, or text lists) into an official Konami KDE Deck Registration Sheet PDF. It also names distinctive features, full category tables and Unicode name handling, which make it clearly different from generic PDF/image export 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?

The intended use is implied: generate a tournament deck registration PDF from a deck list. However, the description does not explicitly say when to choose this over sibling tools such as ygo_generate_proxy_pdf, ygo_render_deck_image, or ygo_export_deck, nor does it state prerequisites or exclusions.

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