Get saved delivery locations

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

Given no annotations, description adequately discloses read-only nature and lack of side effects ('does not change location headers or baskets'). Could mention authentication requirements or rate limits, but still clear.

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, no redundant words, front-loaded with main action first. Highly efficient.

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?

Covers core behavior and read-only guarantee. Lacks output structure description, but tool is simple and no output schema exists. Adequate for its purpose.

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?

Parameter `match_text` is fully described in the schema (100% coverage). Description adds 'identify the current saved-location match' but does not significantly augment schema details. 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?

Description clearly states the verb 'Read' and resource 'authenticated saved Glovo delivery locations', adding nuance about identifying matches. It distinguishes from sibling tools like glovo_set_location by emphasizing read-only behavior and no side effects.

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?

Implicitly indicates usage for reading saved locations or finding a match, and states it is read-only. However, it does not explicitly compare to siblings like glovo_get_location, which might also read location data.

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