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

With no annotations provided, the description carries the full burden. It implies a read-only listing but does not say whether results are exhaustive, ordered, cached, or filtered to a default game, and the presence of a notification_message parameter (unexplained) leaves the side-effect profile ambiguous.

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?

Two compact sentences with the core purpose front-loaded and the downstream usage hint second; nothing is wasted, though the brevity contributes to the behavioral gaps.

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?

For a simple 3-param, no-annotation, no-output-schema read tool, the description is close to adequate but omits what a returned series looks like (name, slug, game) and how it relates to list_sets, both of which an agent needs to chain calls 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 coverage is 67%: search and notification_message have their own descriptions, and game is an enum. The tool description adds no meaning to any parameter, so it neither compensates for the gap nor adds value over the schema, making the 3 baseline appropriate.

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+resource ('List available card series') with a concrete example and notes that the slug feeds search_cards. However, it never distinguishes 'series' from the sibling tool list_sets, which an agent will inevitably confuse.

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 line about the slug being usable in search_cards implies a workflow (discover series, then search cards), but there is no explicit guidance on when to use list_series versus list_sets or when to pass the game filter.

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