Browse stores

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

No annotations provided, so description carries burden. Implies non-destructive read operation ('browse live stores'), but lacks details on authentication requirements, rate limits, or pagination behavior beyond parameter names. No mention of whether it returns full store list or paginated results.

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?

Two sentences: first states main action and resource, second provides critical category_id details. No unnecessary words, front-loaded with 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 no output schema and no annotations, the description omits expected return format (e.g., list of stores with fields) and pagination details. Does not mention that a location must be configured. Adequate for a simple browse, but could be more 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 100% with descriptions for all parameters. Description adds value by enumerating specific category_id mappings (1,3,4) beyond the schema's 'Default 4 (groceries); use 1 for food.' This helps agent select correct category.

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?

Clearly states 'Browse live Glovo stores for the configured location' with specific verb and resource. Provides category_id mappings (1=restaurants, 4=groceries, 3=pharmacy/beauty) that distinguish it from sibling tools like glovo_search_store_items.

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 explicit guidance on when to use this tool vs. siblings like glovo_search_store_items or glovo_get_store_order_options. Does not mention prerequisites such as setting a location first via glovo_set_location.

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