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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about the curated dataset (450+ spots) and geographic scope, but does not disclose return format, ordering, or potential limitations.

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, with the first sentence delivering the core purpose and the second offering practical example queries. It is concise, front-loaded, and contains no filler or redundant information.

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?

With no output schema and simple optional parameters, the description provides enough context for an AI agent to select and invoke the tool correctly. It covers scope, examples, and usage triggers, though it does not describe the result format; this is acceptable for a straightforward discovery tool.

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 has 100% description coverage for all four parameters, so the schema already documents each parameter. The description adds example query values and category examples, but these are illustrative rather than essential, keeping it at the baseline for schema-heavy coverage.

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 specifies the tool's function: finding restaurants, coffee shops, poke bars, ramen, bakeries, and food trucks in Waikiki and across Oahu. It distinguishes itself from sibling tools by focusing on dining/food, whereas siblings cover deals, weather, itinerary planning, events, and tours.

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 explicitly provides example user queries that should trigger this tool ('where should I eat in Waikiki', 'best poke on Oahu'), giving clear usage context. It does not explicitly state when not to use it or name alternatives, but the examples make the intended use evident.

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