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

Annotations already declare the read-only/open-world profile, but the description adds material behavior they cannot express: the account-request accounting model ('one admitted API call consumes one shared account request, including admitted errors'), the no-retry/no-split policy, and the separate handling of unavailable_ids. This is exactly the kind of operational context an agent needs before invoking.

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 and mostly dense, but the no-retry policy is stated twice ('Never split or retry automatically' and 'No automatic retries'), which is redundant. Otherwise tight and earning its place.

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 an output schema present, return values needn't be explained, and the description covers limits, request accounting, and the unavailable_ids split. The one gap is that compact vs full behavior is unaddressed, but overall an agent has enough to call it correctly.

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 low (0% by context signal), so the description must compensate. It conveys the ID semantics ('mixed-game tcg_ IDs', deduplication) and the per-tier limits that map to card_ids/maxItems, but the 'view' enum (compact/full) is never explained in either the description or the schema, leaving one parameter undocumented.

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?

States a specific verb (Read), resource (EUR prices), and scope (mixed-game tcg_ IDs in one request), which cleanly separates it from the single-item siblings get_prices and get_card_prices. An agent can identify it as the batch variant without opening the schema.

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 batch usage ('mixed-game tcg_ IDs in one request') and gives tier-based ID limits, which is useful context, but it never names when to prefer this over get_prices/get_card_prices or get_price_history, leaving the routing decision to inference.

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