find_cheapest

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full responsibility for behavioral disclosure. It only states a basic purpose and reveals nothing about how results are ordered, whether location is mandatory, or what the output format is. This is no more informative than the tool name itself.

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 a single, short sentence with no redundant words, making it concise and easy to parse. It is front-loaded and efficient, though it essentially restates the tool name without providing deeper insight.

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 tool has three required parameters, no annotations, and no output schema, making it moderately complex. The description is too bare—it does not explain the role of latitude and longitude, what a result looks like, or any edge cases. This leaves the agent under-informed.

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?

The input schema provides full descriptions for all three parameters (keywords, latitude, longitude) in Turkish, giving a schema coverage of 100%. The tool description adds no extra semantic value beyond what the schema already states, so the baseline score of 3 applies.

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 finds the cheapest products, using a specific verb and resource. It distinguishes from siblings like compare_prices by focusing on 'cheapest' rather than comparison, but does not explicitly mention how it differs from other price-related tools.

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?

Usage is implied by the description and tool name: use this tool when you want the cheapest products. However, no explicit guidance is given about when not to use it or which alternative tools (e.g., compare_prices, search_products) might be more appropriate in certain scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.