Search cards

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

No annotations; description discloses pagination and compact summary but doesn't detail return format, rate limits, or authentication. Moderate transparency.

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?

Two dense sentences plus reference URL. Front-loaded with key info (full-text, syntax, examples, pagination). No redundancy.

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?

Covers query syntax and pagination but omits output format details (what is a compact summary?) and sibling differentiation. Adequate but with 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 coverage is 100%; description adds value with query syntax examples and pagination context, enhancing understanding beyond schema descriptions.

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?

Description clearly states full-text card search using Scryfall syntax, distinguishing it from siblings like get_card_named (exact name search). Examples and pagination info add specificity.

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 implies usage for complex queries but lacks explicit when-to-use vs alternatives (e.g., when to use get_card_named for exact name). No exclusions provided.

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