Encontra o menor preço vigente de um produto em Lages, Santa Catarina, usando dados estruturados do Menor Preço Hoje. Use quando o usuário perguntar onde determinado produto está mais barato.
| Name | Required | Description | Default |
|---|---|---|---|
| product | Yes | Produto procurado. Exemplo: costela bovina. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of disclosing behavior. It explains the source and geographic scope, but does not mention output shape, freshness of the price data, or any limitations. I believe the lookup-style behavior is reasonably clear, but the description could offer more detail about what the agent and user should expect.
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 compact: two sentences, with the core purpose front-loaded and the use case stated immediately after. Every sentence contributes useful information and there is no redundancy or filler.
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 lookup tool, the description covers the main purpose, the location, the data source, and the trigger. It could be slightly more complete by clarifying what the response will contain, but the tool's simplicity means the current description is largely 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 description coverage is 100%, with 'product' already described as 'Produto procurado' and accompanied by an example. The description adds no additional parameter-level detail beyond restating the product context, so it stays at the baseline for fully documented schemas.
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 a specific action: finding the current lowest price of a product in a specific city using structured data from Menor Preço Hoje. This goes beyond a simple restatement and gives the agent a concrete sense of what the tool does, though it does not explicitly contrast it with sibling tools like search_offers or top_offers.
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 provides an explicit trigger: 'Use quando o usuário perguntar onde determinado produto está mais barato.' This gives clear context for when to invoke the tool, but it does not describe when not to use it or how it compares to the sibling alternatives.
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.
best_price, compare_offers, and search_offers all relate to product pricing and offers, which could cause an agent to choose incorrectly. However, each has a distinct output: best_price for the single lowest price, compare_offers for multi-supermarket comparison, and search_offers for general discovery.
All tools use lowercase snake_case and most follow a verb_noun pattern (compare_offers, list_markets, search_offers). best_price and top_offers deviate slightly by leading with a noun/adjective, but the style remains consistent and predictable.
Five tools is well-scoped for a local price-comparison service, covering discovery, comparison, and market listing without redundancy.
The tool set covers the main user intents: finding the best price, comparing offers, searching products, and listing markets. Minor gaps like retrieving individual market details or historical prices exist but are not core to the stated purpose.