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

With no annotations, the description carries the full burden, and it delivers: it explains searchable fields, that rarity/condition words are ignored, that set-based queries produce separate printings, the presence of a 'set' field on results, and a fallback strategy. This materially shapes agent behavior beyond the raw schema.

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 longer than average but well-structured: purpose and trigger conditions up front, then a tight bulleted search guide. Every bullet earns its place by changing how the agent forms queries or routes results.

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?

Given zero annotations, zero output schema, and minimal parameter descriptions, this description is unusually complete. It covers result contents, downstream integration through product_id, pricing, query constraints, and troubleshooting steps. No critical information needed to invoke the tool correctly is missing.

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. It richly explains query semantics: card name alone, adding the set, avoiding rarity/condition terms, and retrying with plain card names. It leaves the optional 'game' and 'limit' parameters mostly implied by their names/defaults, which is a minor gap.

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 names a specific verb ('search'), a bounded resource ('449K+ TCG products across 25+ card games'), and concrete return values ('card names and IDs, plus current market prices'). It clearly positions this as the lookup/entry-point tool for TCG cards, distinct from downstream tools like card_forecast and grade_or_not.

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?

It gives explicit trigger conditions: a user asks about a specific card, wants to find cards, or needs current pricing. It also instructs the agent to pass product_id to downstream tools. However, it does not explicitly contrast this with sibling lookup-ish tools like market_snapshot or trending_cards, nor does it state when not to use it.

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