pandamart_store_search

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains that results include real prices, stock, availability, plus total_products and has_more for pagination. This clearly conveys that it is a read-oriented search operation and what the caller can expect back.

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 compact and front-loaded with the core purpose. The first two sentences are somewhat redundant ('Search for products' vs 'Searches by keyword'), but the contrast with the curated showcase and the output summary earn their place.

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 no output schema, the description covers what is needed: scope (single darkstore), search mechanism (keyword), what results contain (prices, stock, availability), and pagination fields. Combined with the fully documented schema, an agent has enough context to select and invoke this tool correctly.

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 coverage is 100%, so the schema already documents all six parameters. The description adds only broad behavior — keyword search and pagination via page/limit — without adding parameter-specific meaning beyond what the schema already states.

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 uses a specific verb and resource: 'Search for products within one pandamart darkstore.' It also differentiates itself from the curated product showcase by stating it reaches the store's full catalog by keyword, making it easy to distinguish from sibling tools like pandamart_store_products.

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 gives clear context: this is the keyword-based search over one darkstore's full catalog, equivalent to the search box on a store page. It mentions an alternative approach ('the product showcase's curated shelves') without explicitly naming a sibling tool, so it stops short of a full when-to-use versus when-not-to-use statement.

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