Browse Rappi stores (web)

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

Annotations already declare readOnlyHint=true, so the description's 'Read-only' adds no new information. It adds 'Web-gateway' as a mild behavioral hint about access method, but doesn't disclose return format, pagination, or other traits. Given annotations cover safety, this is acceptable but minimal.

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 terse and easy to read, but it's under-specified rather than efficiently concise. It lacks any structured breakdown of what the tool returns or how to use it, so it doesn't earn high marks for structure.

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 no output schema and undocumented parameters, the description should explain what the agent will get back and how to control output. It does neither, leaving significant gaps for a browse operation that should clarify its data format and privacy options.

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% and the description provides no explanation of privacy_mode or response_format parameters. The agent must infer meaning solely from enum values (summary/structured/raw, markdown/json), which is insufficient for correct invocation.

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 action ('browse stores') and resource, and explicitly differentiates itself from rappi_search_stores by calling itself a complement. However, 'web-gateway' is vague and doesn't clarify what kind of store list this returns or how it differs from other browsing tools like browse_catalog.

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 only says 'Complements rappi_search_stores,' which gives a hint of relationship but no explicit when-to-use or when-not guidance. There is no mention of alternatives like browse_catalog or conditions that would favor this tool over search_stores.

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