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

Annotations already establish readOnly and openWorld, so the description's added value is per-call behavior: a hard cap of 15 results, public-only reveals, the fields returned, and the important caveat that uncovered packs can return an empty list. That empty-result disclosure is exactly the kind of context annotations cannot carry.

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?

Three tight sentences with the result cap and returned fields front-loaded, then parameter guidance, then the failure mode. No filler or redundancy.

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 and annotations covering safety, the description only needs to supply scope, the 15-item cap, and the empty-list caveat, all of which it does. It is slightly silent on ordering/freshness semantics (how 'recent' is defined, whether results are time-sorted).

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 100%, so checklist_id is already documented in the schema; the description mainly restates optionality and adds where to source the UUID plus the empty-result consequence. Useful reinforcement, but little new semantic detail about format or behavior beyond what the schema provides.

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 and resource ('Fetch up to 15 recent public Instant Rips card reveals') and enumerates the returned fields (card and pack titles, item type, time, images). It is clearly distinguishable from siblings such as fanaticscollect_instant_rips_packs or fanaticscollect_instant_pack_releases, which serve different roles (pack lookup vs. individual release detail).

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?

Explicitly tells the agent how to choose between the general feed (omit checklist_id) and a narrowed feed (pass a UUID from fanaticscollect_instant_rips_packs), naming the sibling that supplies the ID. It doesn't state when to prefer this tool over other release-related siblings like fanaticscollect_instant_pack_releases, so it falls short of full when/when-not coverage.

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