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

With readOnlyHint, idempotentHint, and destructiveHint=false already supplied by annotations, the description adds useful behavioral context by listing the full shape of returned offers and noting that requests are handled externally by a human. It does not discuss pagination, limits, or authentication, but for a read-only lookup with no output schema it discloses enough to set expectations.

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 the resource and contents, followed by parameter sourcing guidance and a boundary note about external request submission. It is reasonably tight, though the enumeration of offer fields could be compressed if brevity were the priority.

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 appropriately enumerates the returned offer fields and mentions the request link. It is complete for a two-parameter read-only detail tool, with only minor omissions such as pagination or result limits if they exist.

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 baseline is 3. The description reinforces that brand_slug and article should come from check_parts or search_parts, adding provenance beyond the schema's brief field descriptions, especially for article. It does not otherwise add format or validation details.

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 clearly identifies the resource as the card of a non-liquid showcase position and enumerates exactly what it contains: all seller offers with price, quantity, shipping city, seller, reconciliation date, and condition notes. It also names sibling tools check_parts and search_parts as the sources for brand_slug and article, so an agent can distinguish this detail lookup from those search operations.

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 workflow guidance: take brand_slug and article from the responses of check_parts or search_parts. It also states that the linked request must be filled in by a human on the site, which sets a clear boundary on what the tool does not do. It does not explicitly say when not to use this tool versus the siblings, but the implied sequence is clear.

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