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

Beyond the safety annotations (readOnly/idempotent/non-destructive), the description discloses substantial behavior: versioned snapshot provenance from rebeccabelleboutique.com and Poshmark, 1 USD = 1 USDC price equivalence (not a merchant quote, tax/shipping excluded), null = unverified, sold-out listings labeled, no checkout/orders/escrow, and free anonymous read with no wallet proof. This is exactly the extra 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?

The purpose is front-loaded well, but the block is dense and includes a long list of filtering parameters (store, query, size, brand, category, min_price, max_price, nwt, sort, page, page_size) that are irrelevant to a single-id detail tool, bloating an otherwise small operation.

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 one-param read tool with no output schema, it covers provenance, price semantics, availability labeling, no-checkout, and free access, and it names what is returned (full listing details and collection notes). Its completeness is slightly undermined by instructions that describe parameters this schema does not accept.

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?

With one required param at 0% schema coverage, the description compensates by explaining that the id comes from boutique-list-products and by enumerating live-inventory ID prefixes (rb-#####, mm-#####, lc-#####). That adds real meaning for the otherwise undocumented id. It loses a point for also listing many store/query/size/brand params that do not exist in this schema.

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 states a clear verb+resource+scope: read one curated piece by exact ID, sourced from boutique-list-products, returning listing details and collection notes. This distinguishes it from the sibling list tool. However, the later sentences describing store-based catalog browsing muddy the single-item purpose, since this tool takes only an id.

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 implies usage by pointing to boutique-list-products as the ID source and describes the legacy nine-piece snapshot path, but never states explicitly when to use this vs. list-products or any exclusions. The 'Supply store=... to browse the full catalog' guidance does not apply to this tool's schema and misdirects rather than clarifies.

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