get_live_priceAktualna cena produktu (SKU) w wybranej walucie: cena od (7-10 dni) i cena 24h jeśli od ręki, wraz ze znacznikiem czasu ostatniej aktualizacji ze spotu. Termin płatności 24h != gwarancja ceny.
| Name | Required | Description | Default |
|---|---|---|---|
| sku | Yes | ||
| ilosc | No | ||
| waluta | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds context about returning two price types and a timestamp, plus a disclaimer that payment term 24h does not guarantee the price. This goes beyond annotations, though the exact response structure is not fully described.
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 two sentences and front-loads the core purpose. However, it is written in Polish, which may hinder an English-speaking agent. The phrasing is somewhat verbose and could be more succinct. The caveat about payment term is useful but adds length.
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?
The description covers the main purpose and a behavioral caveat, but it is incomplete due to the missing parameter explanation and lack of output schema. For a simple price retrieval tool, it is minimally adequate but has notable gaps.
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 has 0% description coverage, so the description must explain parameters. It mentions SKU and selected currency, covering two of three parameters. However, it omits the `ilosc` (quantity) parameter entirely and does not clarify the enum values for `waluta`. This leaves significant ambiguity.
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 returns the current price of a product (SKU) in a selected currency, distinguishing it from sibling tools that handle availability, product info, or searches. However, the Polish language and ambiguous phrasing about price types (7-10 days, 24h) slightly detract from clarity.
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 vs. siblings. The description implies it is for price queries, but does not mention when not to use it or provide alternatives. Usage is reasonably inferred but not explicitly stated.
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.
Tools have distinct purposes: check_availability for stock status, get_live_price for current price, get_product for full details, etc. Minor overlap exists (get_product includes price and availability), but descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern using snake_case (check_availability, get_live_price, get_product, list_brands, list_categories, search_products). No mixing of conventions.
6 tools is well-scoped for a product catalog feed. Each tool serves a clear informational purpose without redundancy, and the count is neither too few nor excessive.
The tool surface covers core catalog operations: listing brands/categories, searching, getting details, checking availability, and live pricing. Minor gaps (e.g., no tool to list supported currencies) but overall sufficient for the domain.