tcg_pricing_get_card

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

Adds detail about provider selection logic (always queries Pokémon TCG API, conditionally queries PriceCharting) that goes beyond annotations (readOnlyHint, etc.). No contradiction.

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?

Very concise; two short paragraphs. First sentence nails purpose, rest explains logic. No filler.

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 routing behavior well. Output schema exists, so return format need not be explained. Could mention error handling or fallback behavior, but not necessary given annotations.

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 descriptions are already thorough (query format, grade conditions, provider enum). The tool description adds context about the smart‑routing strategy but doesn’t repeat param details.

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 does 'smart-routed price lookup' for a single card, combining multiple providers. It is distinct from siblings like tcg_pricing_search (search) and tcg_pricing_get (likely similar but less intelligent).

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?

Describes the routing strategy and when `prefer_provider` can override. Implicitly suggests this is the go‑to for single card pricing, but does not explicitly list alternatives or 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.