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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses the per-call cost, clarifies that sales volume and view counts are absent, explains that risk percentages are regime-level constants rather than per-card fits, and states the coverage of 25+ TCG games. It does not cover auth or response structure, but the major behavioral caveats are addressed.

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 front-loaded with the core ranking behavior, followed by a correction note, risk-model caveat, scope, pricing, and usage triggers. It is longer than minimal but each section adds meaningful context. The structure is clear, though the correction note adds complexity.

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?

The description provides enough context for a default call and gives important caveats, but it lacks any meaningful parameter semantics and does not describe the response shape beyond referencing `ranked_by`. Since there is no output schema and no annotations, these omissions leave the agent with partial but not complete information.

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%, and the description does not explain `game`, `limit`, or `min_price` at all. The only indirect hint is 'Covers all 25+ supported TCG games', which loosely suggests the `game` parameter but provides no format, allowed values, or empty-string semantics. The description must compensate for the fully undocumented schema and does not.

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 returns top trading cards ranked by PRICE VELOCITY (drift), with highest absolute movement first. It also explicitly corrects a prior misconception about sales volume, which sharpens the core purpose and distinguishes it from volume-based market tools.

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 gives explicit trigger phrases like 'what cards are hot right now?', which is useful guidance. However, it also includes 'what's selling the most?' immediately after disclaiming that sales volume is NOT in the dataset, creating a mixed signal. It does not name alternatives or explain when not to use this tool.

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