get_product_detailsFetch full product detail by slug: description, specs, photos, pricing tiers, available physical units, and categories.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Product slug from search_products results |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true and openWorldHint=true, so the description's disclosure of read-only behavior is redundant. However, it adds transparency by listing the kinds of data returned (pricing tiers, physical units, categories), which helps the agent understand the scope. No contradictions.
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?
A single, front-loaded sentence that efficiently conveys all necessary information. No wasted words.
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 compensates by listing the expected return fields (description, specs, photos, etc.). This is sufficient for a get-detail tool. Lacks mention of error handling or size limits, but overall complete.
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%: the only parameter 'slug' has a description 'Product slug from search_products results'. The description's 'by slug' adds no new meaning beyond the schema. 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 clearly states the verb 'Fetch' and the resource 'full product detail', and enumerates the specific components (description, specs, photos, etc.). This distinguishes it from siblings like search_products which returns slugs, and check_availability which focuses on stock.
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 implies you need a slug from search_products (stated in parameter description), but provides no explicit guidance on when to use this tool versus alternatives, nor when not to use it. Usage context is implied rather than articulated.
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.