Get a set

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

No annotations provided. Description covers the basic behavior (fetch single set by IDs) but does not disclose potential errors, return format, or any side effects. Adequate for a simple read operation.

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?

Single sentence that conveys all necessary information with an example. No wasted words.

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 a simple fetch tool with no output schema and clearly defined optional parameters, the description covers the core functionality. Could mention return object type but not strictly necessary.

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 coverage is 100% with each parameter described (id, code, tcgplayer_id). Description adds overall purpose but no additional semantic detail beyond the schema.

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 specific verb 'Fetch' and resource 'single set' with three identifier examples (set code, Scryfall ID, TCGplayer group ID). Clearly distinguishes from sibling tool 'list_sets' which lists all sets.

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?

Description states when to use (fetch by any of three identifiers) but does not explicitly mention alternatives or when not to use (e.g., listing all sets). Context is clear enough for basic cases.

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