search_card

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

Discloses default sorting (price_czk ascending), exclusion of non-playable cards, and shop filtering logic. No annotations exist, so description carries full burden; it is thorough but omits rate limits or auth requirements.

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?

Front-loaded with purpose and output details. Reasonably concise, though the shop logic explanation could be more terse. No wasted sentences.

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 6 parameters and no schema descriptions, the description covers most critical aspects but omits 'edition' and 'in_stock_only' semantics. Output schema exists but isn't shown; still, the return field list is provided.

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 0%, so description must explain all parameters. It explains shops, exclude_shops, and include_non_playable, but does not mention the 'edition' parameter or the 'in_stock_only' default behavior. This leaves gaps.

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 clearly states the tool searches Magic cards across Czech shops and returns sorted offers. It distinguishes from sibling tools like lookup_card (card details) and list_shops (shop listing).

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?

Provides clear context for shop filtering (allow/deny lists) and when to include non-playable cards. Does not explicitly state when not to use this tool versus alternatives, but the sibling context helps.

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