list_restaurants

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

No annotations provided, so description must handle behavioral disclosure. It only notes listing and filtering; no mention of side effects, auth requirements, or data freshness. The agent cannot infer safety or mutability.

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?

Very short, single sentence; front-loaded but omits important details. Could be expanded without becoming verbose. Acceptable but minimal.

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 4 parameters and no schema descriptions, the description should provide comprehensive context. It only covers one parameter partially. Output schema exists but doesn't excuse missing parameter explanations.

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 0%, so description should compensate. It adds meaning only for 'query' (filter by name). Other parameters (limit, zone_id, open_only) remain unexplained. Default values exist but their effect is unclear.

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 action ('List'), resource ('AVAS restaurants'), scope ('Maldives delivery zone'), and optional filter ('by name'). It distinguishes from siblings like get_restaurant which retrieves a single restaurant.

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?

No guidance on when to use this tool versus alternatives like get_restaurant or search_menu_items. No exclusions or prerequisites mentioned.

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