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

Annotations only declare readOnlyHint and openWorldHint; the description adds useful context beyond that: a hard cap of 100 matches returned, the shape of each result, and the available narrowing and sorting levers. It does not mention rate limits, pagination, or whether truncation past 100 can be paged, which keeps it from a 5.

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 with the purpose in the first clause, then the return shape, then the levers, then the hand-off — good ordering with no filler. It dedicates a long clause to enumerating returned fields that the output schema already declares, which is the one redundancy worth trimming.

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 a full output schema, safety annotations, and 100% schema coverage, the description only needed to add scope, result cap, and the next-step tool — and it does all three without leaving an agent guessing on how to call it.

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 all four parameters are already documented at the field level; the description mostly restates them (sort options, console_uid narrowing, exclude_variants). Baseline 3 applies since the schema does the heavy lifting and the description adds no syntax or format detail beyond it.

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 ('Search PriceCharting's collectibles price guide') and even enumerates covered categories, making scope unmistakable against a large sibling list. It distinguishes itself from pricecharting_product by naming that sibling as the deeper-detail follow-up.

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 routes the agent: use pricecharting_product for a match's full price guide and recent sales, implying this tool is for discovery/matching. However, it never contrasts with other plausible siblings such as pricecharting_console, pricecharting_categories, or pricecharting_big_movers, so a few selection questions remain open.

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