Browse Rappi catalog

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

The description repeats 'Read-only', which is already declared by readOnlyHint=true, and adds nothing else about behavior. It does not disclose output format, pagination, or any side effects beyond what annotations already cover. The 'Optional lat/lng' is parameter-related, not behavioral.

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 short and to the point, with no redundant sentences. However, the cryptic phrase 'restaurant-bus' is confusing and detracts from clarity, though it does not make the text verbose.

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 6 parameters, no parameter descriptions in the schema, no output schema, and many sibling tools, the description is severely incomplete. It gives only a basic idea of the tool's function and fails to explain how parameters affect results, how to control privacy_mode, or what the output looks like.

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 0%, so the description must compensate. It only explains the optional lat/lng parameters, while limit, query, privacy_mode, and response_format are left undocumented. This partial coverage does not sufficiently aid an agent in using the parameters correctly.

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 verb ('Browse') and a resource ('store catalog'), but 'Nearby' and 'restaurant-bus' are vague and do not clearly differentiate from sibling tools like rappi_browse_stores. The purpose is understandable but not specific enough to distinguish it from similar browsing tools.

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 mentions 'Nearby' and 'Optional lat/lng', implying it is for location-based browsing, but it provides no explicit guidance on when to use this tool over alternatives such as search_stores or browse_stores. No exclusions or alternatives are mentioned.

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