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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the available markets and a list of returned fields, but says nothing about proximity radius, ordering by distance, pagination behavior, or rate limits.

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 compact sentence with no filler. It front-loads the resource and scope, though the trailing colon-list of return fields is somewhat listy and duplicated by the output schema.

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?

Adequate for a read-only nearby search whose annotations and output schema carry most of the load, but it omits proximity/radius semantics and any disambiguation from the near-identical pandamart_store_search sibling, leaving real gaps for an agent choosing between them.

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 100%, so latitude, longitude, limit, offset and market are all documented in the schema. The description restates the market enum values that the schema already provides, adding no syntax, defaults, or meaning beyond it — the baseline 3 applies.

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?

Clear verb+resource: 'pandamart ... darkstore search near a location', with a parenthetical clarifying the parent brand and vertical. It reads as a nearby darkstore search, distinguishable from the plain pandamart_store fetch, though it doesn't explicitly name what separates it from pandamart_store_search.

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 when-to-use guidance and no alternatives named. The sibling set contains pandamart_store, pandamart_store_search, and foodpanda_search, none of which are mentioned, so the agent must infer selection criteria from names alone.

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