get_restaurant

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

Without annotations, the description should disclose behavioral traits. It only says 'public details', hinting at read-only access, but does not clarify if authentication is needed, whether the tool is safe to call repeatedly, or what 'AVAS' means. Minimal behavioral context.

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 a single, front-loaded sentence with no extraneous words. It efficiently conveys the core purpose.

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 the output schema exists, the description can be brief. However, with 2 parameters and no annotations, it lacks guidance on usage context (e.g., how to obtain merchant_id, relationship to list_restaurants). Adequate but not thorough.

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 the description must compensate. It adds no explanation of the parameters beyond what is in the schema (e.g., zone_id default, meaning of merchant_id). The schema already provides titles, but the description offers no additional semantics.

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 verb 'Get', the resource 'public details for one AVAS restaurant', and the method 'by merchant ID'. It distinguishes from sibling tools like list_restaurants (which lists) and get_menu (which gets menu details).

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 implies you need a merchant ID to use the tool, but it does not explicitly state when to use this tool over alternatives (e.g., list_restaurants to get an ID) or when not to use it. No guidance on prerequisites or context.

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