therealreal_collection

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

With no annotations, the description carries the transparency burden and does well: it states 'Credential-free public data,' identifies the source as The RealReal's server-rendered collection page, indicates the output is a normalized page, and documents pagination behavior. It does not go into rate limits or error behavior, but those are not essential for this simple browse operation.

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 core action and uses only four sentences, each carrying useful information (purpose, example/distinction, pagination, data source). There is minor redundancy in repeating 'The RealReal listings' and 'browsed by... slug,' but no wasted sentences.

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?

Given no output schema, the description covers the important context: what is returned, how to paginate, where the data originates, and that no credentials are needed. Combined with the schema's pointer to the collections endpoint for slug values, an agent has enough to call this tool correctly, though a bit more detail on normalized listing fields would improve completeness.

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%, so the baseline is 3, but the description adds real value beyond the schema by illustrating what a collection slug looks like ('on-sale-now') and what kinds of collection qualify ('sale campaigns, editor's picks'). Pagination semantics are reinforced by explaining the next_after round-trip.

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 clear, specific verb and resource: 'Browse The RealReal listings by curated collection.' It gives a concrete example ('on-sale-now') and explicitly positions this as merchandising-collection browsing 'distinct from category/designer browsing,' making it easy to tell apart from the many therealreal_* siblings.

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 explains when this tool is appropriate ('curated collection slug... sale campaigns, editor's picks') and excludes category/designer browsing. It also tells the user how to page through results with next_after. It could be stronger by naming the sibling tool that lists available collection slugs, though the schema partially covers this.

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