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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral detail beyond that: query content words are matched individually, filler words are ignored, results are ranked with a 0-100 score, and the response includes price tier, neighborhood, happy-hour info, and a link. No contradiction with annotations.

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: three sentences that front-load the purpose and city behavior, then cover return fields and query strategy. There is no fluff, repetition, or unnecessary restatement of schema details. Every sentence contributes useful 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?

For an 11-parameter, all-optional tool, the description covers the essential behaviors: city scoping, query semantics, output contents, and combining filters. The output schema and annotations fill most remaining gaps. It could be more explicit about routing between this tool and the generic 'search' sibling, but an agent has enough context to invoke the tool 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 description coverage is 100%, so the input schema already documents all 11 parameters in detail; the baseline is 3. The description reinforces query matching semantics and provides useful examples, but it does not add substantial per-parameter meaning beyond what the schema already states. It earns some credit for the city behavior and keyword guidance, but not enough to exceed the baseline.

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 states a specific verb and resource: it searches Dim Hour's restaurant, bar, and venue catalog. It also clarifies the core scoping decision (pass city vs. omit for all venues), which helps an agent understand what the tool targets. It stops short of 5 because it does not explicitly differentiate itself from the generic 'search' sibling.

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 gives clear context for using the tool: pass city to narrow to one city, omit it to search all 19,000+ venues, and use one strong keyword rather than a sentence. It also advises combining with filters. However, it does not mention alternatives or exclusions relative to siblings like 'search' or 'list_*', so it lacks explicit when-not-to-use guidance.

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