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

Beyond the readOnlyHint/idempotentHint annotations it discloses OAuth scope (store:read), the approved-store requirement, that prices exclude shipping and tax, that graded and raw copies are distinct, that estimates and asks are not sold transactions, and that missing costs mean unknown profit. It also enumerates failure modes (invalid fields, unavailable stores, foreign or deleted targets, provider failures) and the response envelope shape.

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 scope and non-mutation constraints are front-loaded, which is good, but the text is padded: 'Use supercatch_get_pricing_context for this read in the connected account' and 'Supply only the fields in its strict input schema' add nothing, and read-only/no-write is restated three separate times despite the annotations. Several sentences could be cut without losing information.

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 single-parameter read tool it covers authorization, store eligibility, data semantics (asks vs estimates vs transactions), tax/shipping exclusions, error behavior, and envelope versioning. With an output schema present, no further return-value explanation is needed, so nothing an agent needs before calling is missing.

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% and the schema already spells out the 1-5 item limit, uniqueness, and the 'never substitute a display label' rule. The description only reinforces 'exact owned' and the five-ID cap, adding little beyond the structured field, so the baseline 3 applies.

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 opening sentence names a specific verb and resource (read direct price evidence) and bounds the scope to up to five exact owned listing IDs, explicitly contrasting with repricing-plan and write workflows. That contrast implicitly separates it from prepare_card_price_updates and supercatch_get_price_plan, though it never names a sibling outright.

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 states prerequisites (approved owned store, store:read consent) and a recovery rule (expired cursors require a fresh search), which is real usage context. However, the only routing sentence is circular — 'Use supercatch_get_pricing_context for this read in the connected account' — and there is no explicit statement of when to prefer this over preview_card_prices or supercatch_get_price_plan.

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