Get card prices

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

With no annotations, the description carries full burden. It states the return includes prices and links, but does not disclose potential side effects, authentication needs, rate limits, or operational details like caching or response pagination. For a read-only tool, this is minimally adequate.

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 a single, well-structured sentence that conveys purpose and identification methods without extraneous information. Every part serves a clear function.

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 the absence of an output schema, the description adequately explains the tool's functionality and parameter usage. It could be improved by briefly noting the expected return structure (e.g., array of prices or single object), but is still reasonably complete for a pricing lookup tool.

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?

The description adds meaning beyond the schema by grouping parameters into identification strategies (id, name, set+collector_number) and explaining that fuzzy matching applies to the name parameter. This clarifies usage beyond the individual parameter descriptions, which already have 100% coverage.

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 that the tool returns market prices in multiple currencies and purchase links, and specifies three identification methods (id, name, set+collector_number). This distinguishes it from siblings like get_card_by_id or get_card_named, which do not include pricing.

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?

The description implies usage when card prices are needed, but does not explicitly state when to prefer this over alternative tools like search_cards or get_card_collection. No when-not-to-use guidance or alternative tool references are provided.

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