Search locations

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

Discloses that it returns only place id, provider, title, and subtitle – a key behavioral detail beyond the schema. No annotations provided, so description carries burden. Does not mention pagination, error behavior, or auth requirements, but acceptable for a simple search tool.

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?

Single sentence with no wasted words. Includes both action and output description. Well-structured for readability.

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?

Adequately covers purpose and output for a simple search tool with 2 parameters and no output schema. Could mention that it searches only public locations, but not necessary given the title.

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?

Input schema has 100% description coverage for both parameters (query and limit). Description adds no additional meaning beyond schema – baseline 3 is appropriate.

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 'search public Glovo delivery locations by text' – specific verb and resource. Distinguishes from sibling tools like glovo_get_location (single location) and glovo_browse_stores (stores). However, does not explicitly contrast with siblings.

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 guidance on when to use this tool vs alternatives (e.g., glovo_get_location for a specific location, glovo_browse_stores for stores). Implied usage from name and description, but lacks explicit direction.

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