searchSearch this site's content. Returns matching documents (id, title, url); pass an id to fetch for the full text.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query |
| Name | Required | Description | Default |
|---|---|---|---|
| results | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context by stating the returned fields and pointing to fetch for full text, which goes beyond what annotations alone provide.
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 two concise sentences, front-loads the main action, and includes both the return format and the follow-up workflow. Every clause earns its 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 single-parameter tool with strong annotations, an output schema, and a clear follow-up path to fetch, the description is nearly complete. The only notable gap is explicit differentiation from search_products, which could matter during tool selection.
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?
The single parameter query is fully described in the schema ('Search query'), so the description does not need to compensate. It also adds no query syntax or matching semantics, keeping this at the baseline for 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 states a clear action ('Search this site's content') and specifies the return shape (id, title, url), so the agent understands what the tool does. However, it does not explicitly distinguish itself from the sibling search_products, leaving some ambiguity about which search tool to use for product queries.
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 a clear workflow hint: pass an id returned by this tool to fetch for full text. It does not, however, explain when to choose this tool over search_products or list_products, so the routing guidance is only partially complete.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct actions: browse, search, product detail, inventory, recommendations, cart, and store policy. The main potential confusion is between get_product and check_inventory, which both report product/variant price and stock, though list_products vs search_products is reasonably clear from descriptions.
Tool names are consistently snake_case and many follow a verb_noun pattern like check_inventory, get_product, list_products, and search_products. However, best_sellers, related_products, and store_info are noun phrases, while fetch and search are bare verbs, making the naming pattern mixed but still readable.
Eleven tools is well-scoped for an e-commerce shopping assistant covering catalog browsing, product search, inventory checks, recommendations, cart assembly, content search, and store policies. Each tool has a clear purpose and the count is neither bloated nor too thin.
The tool set covers the full shopper-facing journey: discovering categories and products, searching content, viewing product details and stock, seeing best sellers and related items, checking store policies, and building a cart. As a read-only storefront gateway, missing merchant-side operations are outside its stated purpose.