therealreal_category

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

With no annotations provided, the description carries the full disclosure burden. It does well: it reveals the tool returns a 'page of normalized listings', supports cursor-based pagination via 'next_after'/'after', requires no credentials, and sources public data from The RealReal's server-rendered category page. It does not explicitly state read-only behavior or rate limits, but 'Browse' and 'Returns' strongly imply a safe read 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 compact and front-loaded: it opens with the core purpose, then adds pagination and data-source context. Each sentence contributes useful information without repetition or padding.

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 simple category-browsing tool, the description covers the critical operational details: path input, pagination cursor, and public/credential-free access. The absence of an output schema means return values are not fully specified, but 'a page of normalized The RealReal listings' provides a reasonable baseline for agent expectations.

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 schema already documents all four parameters. The description adds value beyond the schema by giving a concrete path example ('women/handbags') and explaining the 'after' cursor mechanics in context ('Pass a previous response's next_after back as after'). It does not detail on_sale/available, but those are already well described in the 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 description states a specific action and resource: 'Browse The RealReal listings by category' and explains the category path with an example ('women/handbags'). It is clear and distinct from siblings like therealreal_search or therealreal_collection, though it does not explicitly name any sibling it is not.

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 clearly indicates when to use the tool: when browsing The RealReal listings by category (taxon) path, with credential-free access. It also explains pagination usage ('Pass a previous response's next_after back as after'). It does not explicitly mention alternatives or exclusions, but the context is clear enough.

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