List stores near the customer

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful result-shape context (open status, minimum order, distance) that matters for selection, but it omits pagination/limit behavior, default ordering, and what happens when no location is supplied.

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?

A single well-formed sentence with the key distinguishing information front-loaded and no filler. It is efficient, though arguably undersized for a six-parameter discovery tool with zero required fields.

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?

For a tool with no required parameters and no output schema, the description covers the essence but leaves real gaps: no guidance on location resolution (saved address vs. coordinates), defaults (limit 20, filter all), or distance units. Adequate, not complete.

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 67%, so the schema already documents city, module, latitude and longitude. The description reinforces the Mart/Bites meaning and the delivery-area scoping but adds nothing about filter (all/popular/latest) or limit, leaving those to bare enum/default values.

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 names the resource precisely — stores (Mart) or restaurants (Bites) that deliver to the customer's area — and lists the decision-relevant attributes returned. It doesn't differentiate itself from siblings like foran_store_details or foran_search_products, and the verb 'list' only appears in the tool name/title, not the description body.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The description never says to use this instead of foran_search_products when the customer wants to browse rather than search, nor does it reference the location requirement (city OR latitude/longitude) that governs a valid call.

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