pandamart_search

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It explicitly states that a location with no coverage returns an empty list rather than an error, which is important behavioral detail. It also mentions the tool returns an empty list instead of erroring, which is a behavioral trait. However, it does not describe whether pagination is automatically handled, whether results are sorted by distance, or if there are any rate limits or authentication requirements. Given the lack of annotations, the description adds significant behavioral context but could be more comprehensive.

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 concise and front-loaded, starting with the main action and returning immediately to the key output. It efficiently lists the returned store details in a single sentence and ends with the empty-list behavior. No wasted words; every sentence adds value. It is well-structured and easy to parse.

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 search tool with 5 parameters and full schema coverage, the description is largely complete. It covers the purpose, the returned fields, and edge-case behavior. It does not explicitly state how results are ordered or how to choose between this and sibling search tools, but given the schema richness and the clarity of the description, an agent can likely use it correctly. Missing explicit mention of pagination behavior is minor given the schema describes limit/offset.

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%, with each parameter having a description. The tool description adds context about the 'code' field in the response which is the value for other endpoints, but it does not add specific parameter-level details beyond the schema. The schema already documents latitude/longitude as search center, limit/offset for pagination, and market with allowed values. The description reinforces the purpose of latitude/longitude but does not further explain format or units. Baseline 3 applies given full schema coverage.

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 tool searches pandamart darkstores near a location, specifying that it returns stores delivering to a given latitude/longitude. It explicitly mentions the location-based search, distinguishes it from sibling tools like pandamart_store (which likely targets a specific store by ID), and clarifies that it returns store details including the code useful for other endpoints. The verb 'search' and resource 'pandamart darkstores' are specific and unambiguous.

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 implies the use case: finding darkstores delivering to a specific location, which is appropriate for users needing delivery information. It does not explicitly state when not to use this tool versus alternatives like pandamart_store_search (which might search by name) or pandamart_store (which retrieves a specific store). However, the emphasis on location-based search and listing stores suggests it is the entry point for location-based queries, and the sibling names provide some context. It could explicitly mention that for a specific store by code, use pandamart_store.

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