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

With no annotations provided, the description fully carries the transparency burden. It discloses accent-insensitive and typo-tolerant matching, relevance ranking, the exact semantics of 'open_now', the ALL-must-match behavior of attributes, and the detailed result shape including hours format and delivery links.

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 dense but every sentence earns its place. It front-loads the core purpose and then efficiently covers query behavior, filters, result fields, and common slugs without unnecessary fluff. The length is appropriate given the tool's complexity and the lack of an output schema.

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 six parameters, no output schema, and no annotations, the description is remarkably complete. It explains not only how to invoke the tool but also what the response contains, including nested structures like the delivery array and hours periods, so an agent can use the results 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?

Although the schema already describes every parameter, the description adds substantial meaning: examples of typo tolerance, the definition of 'open_now' as 'open at this exact moment', the requirement that attributes ALL match, and a list of common amenity slugs. This goes well beyond the structured 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 opens with a specific verb and resource: 'Search for places (restaurants, cafes, shops, etc.)'. It distinguishes itself from siblings like search_dishes by targeting places generally and by describing the available filters, making the tool's purpose unambiguous.

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 clear context: it is for searching places in a neighborhood and supports multi-condition filters. However, it does not explicitly state when to use this tool over siblings such as search_dishes or list_categories, so it stops short of full alternative-based guidance.

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