Get store menu

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

No annotations are provided, so the description carries full burden. It mentions 'compact recursive' but fails to disclose pagination (limit parameter), performance characteristics, or whether the tool mutates any state. Limited behavioral insight.

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 sentence that is front-loaded and contains no fluff. However, its terseness borderline under-specification for a tool with three parameters and no annotations.

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 absence of an output schema, low schema coverage, and three parameters, the description is too brief. It does not explain the return format, error conditions, or how 'limit' works. Basic context for a menu tool is missing.

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?

With only 33% schema description coverage (only 'limit' is described), the description adds minimal value. It does not explain the meaning or usage of 'store_id' or 'store_address_id' beyond the generic context of a store. No parameter-specific semantics are provided.

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 'Return' and the resource 'compact recursive menu/category list for a store'. It distinguishes the tool from siblings like 'glovo_get_store' and 'glovo_get_product' by specifying it returns a menu/category list.

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 provides no guidance on when to use this tool versus alternatives like 'glovo_browse_stores' or 'glovo_search_store_items'. No when-not-to-use or prerequisite context is given.

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