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

With no annotations provided, the description carries the full behavioral burden. It does add genuine value by declaring 'Read-only' and naming the returned payload (full attrs, detail page url, buy url), but it omits auth requirements, rate limits, and what happens for an unknown platform+item_id combination.

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?

A single dense sentence with zero filler; the lookup key and the returned fields are front-loaded, and the read-only note is a short trailing qualifier.

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?

There is no output schema, so the description usefully sketches the return payload (full attributes, detail page URL, buy URL), and it flags the read-only nature. Missing only edge-case behavior for invalid platform/item_id inputs, which is minor for a simple keyed lookup.

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 0% for both parameters. The description names platform and item_id but adds no format, casing, or validity information beyond what the schema already encodes (the platform enum values live only in the schema). It therefore does little to compensate for the coverage gap.

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 ('Get one curated shelf item') and the identifying key ('by platform+item_id'), which separates it from the list-oriented shelf_search sibling. It does not, however, explicitly distinguish itself from lookalike siblings such as cps_item_info or get_goods_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?

The phrase 'by platform+item_id' implies the precondition for calling this tool (you already have both identifiers), but there is no explicit when-to-use vs shelf_search or cps_item_info, and no stated exclusions or failure cases.

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