list_nearby

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

Despite no annotations, the description discloses what the tool returns (compact dicts with slug, rating, ETA, online status, tags), what it does not return (prices), and the default behavior (Tallinn center). It does not cover all edge cases but is transparent enough for safe invocation.

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?

Two dense sentences pack purpose, defaults, return format, query usage, and sibling guidance with zero wasted words. Every sentence 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?

Given 8 optional parameters, no required params, and no output schema, the description effectively explains the return format, filtering options, and when to use the sibling tool. It is complete enough for an agent to select and invoke correctly.

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%, so the input schema already describes each parameter well. The description adds marginal value by reaffirming the default location and the substring-match behavior of `query`, but does not provide significant new insight beyond the schema.

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 'List' and resource 'Wolt venues near a location', specifies the default location (Tallinn center), and distinguishes itself from the sibling tool 'get_menu' by noting that prices are not included here.

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?

It provides explicit guidance on when to use this tool versus the alternative: 'Prices are not included here — call get_menu for a specific slug.' It also explains how to use the `query` parameter for substring matching, and mentions defaults and filtering options.

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