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

The description discloses detailed behavior: reservation date/time filters narrow results to shops with available slots, headcount filtering applies only to tableUnit shops and is ignored for timeUnit shops, and parameter precedence rules (e.g., cityCode over prefecture, smallGenreId over mismatched largeGenreId) are stated. It also warns that reservationTime alone is an error, making the tool's runtime behavior transparent.

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 not wasteful; each sentence adds necessary detail about parameter semantics or tool behavior. Some repetition (e.g., '省略可' appearing many times) is present, but it serves to keep individual parameter notes self-contained. Overall it is appropriately sized given the 13 parameters and their rules.

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 description covers all input parameters and their behavioral effects, but it lacks an explicit output schema or description of the response structure beyond mentioning shopId. Given that no output schema is provided, the agent would have to infer other returned fields, though the primary use (feeding shopId to get_availability) is clear.

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?

All 13 parameters have descriptive comments covering format examples (e.g., cityCode "13113" for Shibuya), default values, maximum constraints (perPage=20), and inter-parameter relationships such as required pairing of reservationTime with reservationDate. This goes well beyond the schema basics and fully clarifies each parameter's meaning.

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's purpose: to search for shops on Ekiten that support online reservations, accepting multiple filters. It also explicitly ties the returned shopId to the get_availability tool, distinguishing it from sibling tools like reservation creation or cancellation.

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 the tool, including the requirement that at least one of the listed filter parameters must be specified. It also explains that detailed conditions (menu, staff, smoking) cannot be filtered here and directs users to use get_availability for those, offering clear usage direction.

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