get_pickup_zonesReturn the pickup/delivery options for a product: each option has type (PICKUP|DELIVERY), location (address + lat/lng), price, and (for delivery) the maximum reachable distance in miles.
| Name | Required | Description | Default |
|---|---|---|---|
| product_slug | Yes | Product slug |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint (safe read) and openWorldHint (results may vary). The description adds behavioral context by detailing the output structure (type, location, price, max distance for delivery), which goes beyond annotations.
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?
Single sentence, front-loaded with purpose, no filler. Every word earns its place.
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 read tool with one parameter and no output schema, the description explains return fields well. However, it could mention pagination or error handling, but given low complexity, it is sufficient.
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% (parameter described as 'Product slug'). The description does not add new meaning beyond the schema, so baseline 3 is appropriate.
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 uses specific verb 'Return' and resource 'pickup/delivery options for a product'. It lists fields (type, location, price, max distance) and distinguishes from siblings like get_product_details or check_availability by focusing on delivery zone options.
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?
No explicit guidance on when to use this tool versus siblings. The description implies usage when needing pickup/delivery options, but doesn't state when not to use (e.g., when product details suffice) or mention alternative tools like check_availability.
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.