search_productsSearch the Green Gooding rental catalog by text query, optionally filtered by NYC zipcode for distance-sorted results. Returns a list of products with id, slug, name, brand, cheapest price, photo, and distance (when zipcode is provided).
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query, e.g. "blender" or "drill" | |
| limit | No | Max results (default 20, max 50) | |
| zipcode | No | 5-digit US ZIP for distance sorting |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true and openWorldHint=true, indicating safe reads. The description adds that results include id, slug, name, brand, cheapest price, photo, and distance when zipcode is provided, which aligns with annotations and provides valuable context beyond them.
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 sentences, front-loaded with purpose, no unnecessary words. Every sentence adds value.
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 search tool with 3 parameters, no output schema, and clear annotations, the description fully explains input purpose, optional behavior, and return fields. No gaps given tool complexity.
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 covers all parameters with descriptions (100% coverage). The description adds context about zipcode enabling distance sorting and lists return fields, but does not significantly enhance parameter semantics beyond 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 clearly states the tool searches the Green Gooding rental catalog by text query, with optional zipcode filtering for distance-sorted results. It lists return fields, distinguishing it from siblings like check_availability or get_product_details.
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 indicates when to use (search by text query, optionally filtered by zipcode) but does not explicitly exclude scenarios or reference alternatives like get_product_details or list_categories for other use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but get_quote and propose_booking both create Stripe checkout URLs with overlapping functionality, potentially confusing an agent on which to use.
All tools follow a consistent verb_noun snake_case pattern (e.g., check_availability, get_pickup_zones, list_categories), making the naming predictable and clear.
With 7 tools, the set covers browsing, searching, quoting, and booking without being overwhelming or too sparse, fitting the rental domain well.
Covers core workflows from discovery to booking initiation, but lacks post-booking management like cancellation or status checks, which is a minor gap for a complete lifecycle.