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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds context: returns 'live resale listings', 'direct buy link', 'all platforms, all sizes, all conditions, with prices wherever a live feed provides one.' No contradictions.

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 concise, with three paragraphs each providing essential information. No fluff or redundant statements.

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?

No output schema exists, but the description explains the output: 'live resale listings with direct buy link', 'all platforms, all sizes, all conditions, with prices.' It mentions that pieces have a collectionId and pieceId and that this tool is used after search_pieces. Complete for a detailed lookup tool.

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%, but the description explains that pieceId and collectionId come from search_pieces and are needed for identifying the garment. It does not describe each parameter individually, but the added context about where to get the IDs compensates.

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 states the verb 'Get' and the resource 'the complete set of live resale listings for one specific garment, with a direct buy link for each.' It distinguishes from siblings by mentioning that search_pieces is called first and that this tool provides all listings for a specific piece.

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 description explicitly says when to use: 'Use this once someone has settled on a specific piece and wants every option available.' It also provides a prerequisite: 'Call search_pieces first: it returns the collectionId and pieceId this tool needs.' Does not explicitly state when not to use, but the context is clear.

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