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

With readOnlyHint=true and openWorldHint=false already present, the description adds substantial context: no auth is required, this is a rules table not a progress report, items with no `requires` are granted to every signed-in member, and condition shapes ({ signal, gte }, { minTier }, { minLevel }) are explained. This goes well beyond the annotations.

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 purpose and usage, and the condition semantics are valuable. It is slightly repetitive (twice states 'No auth required') and includes an Args block that largely duplicates the schema, but the Returns block compensates since no output schema exists.

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 no output schema, the description explains the return shape ({ ok, count, items[{ id, kind, label, blurb?, rarity, requires?, asset? }] }) and the meaning of condition structures. It also clarifies auth requirements and the distinction from progress tracking, leaving no critical gaps for correct invocation.

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 100%, so the single `kind` parameter is already fully documented with its enum. The description restates the same enum values and confirms it is optional, adding no semantic detail beyond the schema; baseline 3 is 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?

The description states a specific resource (the full catalog of Funko Me unlocks) and what it includes (conditions that earn each one). It explicitly distinguishes itself from sibling tools ic_funko_progress and ic_funko_levels, so an agent can tell what it does 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?

It gives explicit when-to-use guidance ('explain to a human WHY something is locked, or to show what is worth doing on the floor') and names the alternative for per-member progress (ic_funko_progress). The reference to ic_funko_levels for level rules further routes the agent correctly.

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