Retrieve The RealReal search-box suggestions for a partial query, returning typeahead results to complete searches.
Get The RealReal search-box suggestions. Returns The RealReal's own search-box typeahead suggestions for a partial query.
| Name | Required | Description | Default |
|---|---|---|---|
| term | Yes | Partial free-text query to get search-box suggestions for |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the tool returns typeahead suggestions, but adds nothing about result count, rate limits, or format, and gives no sense of the safety profile beyond the implied read-only nature of an autocomplete endpoint.
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?
Two short sentences, front-loaded with the action and resource. Slight redundancy in restating 'search-box suggestions'/'typeahead suggestions,' but there is no filler 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 single-parameter autocomplete tool with no output schema and no annotations, the description covers what the tool returns and what input it expects. Given the low complexity, little more is required.
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 single 'term' parameter is already fully documented by the schema. The description's 'partial free-text query' phrasing mirrors the schema rather than adding format or constraint details, so the baseline 3 applies.
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?
Specific verb+resource ('Get The RealReal search-box suggestions') with a scope that names the site and the typeahead nature, which separates it from broader siblings like therealreal_search. It does not explicitly distinguish itself from other therealreal_* retrieval tools, but the purpose is unambiguous.
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 phrase 'for a partial query' hints at the intended input shape but gives no when-to-use guidance against siblings (e.g., therealreal_search for full queries). No exclusions or alternatives are named anywhere in the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.