[instacart · risk:low] Search for grocery items and stores in the Instacart app
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search terms, e.g. "organic bananas" | |
| store | No | Store name or id to scope the search |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It only states that the tool searches for items and stores, lacking any disclosure of behavioral traits such as result limits, location dependency, or error handling.
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 a single sentence plus a risk prefix. It is efficient, though the risk tag could be separated. Still, it is appropriately short.
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?
Given no output schema and no annotations, the description lacks completeness. It does not explain the return format, pagination, or error scenarios, leaving gaps for agent understanding.
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?
Both parameters have descriptions in the input schema (coverage 100%). The main description adds no additional meaning beyond what is already stated in the schema. Baseline 3 is appropriate.
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 for grocery items and stores in the Instacart app. The verb 'Search' and resource 'grocery items and stores' are specific. However, the inclusion of '[instacart · risk:low]' is extraneous and not standard, slightly detracting from clarity.
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 guidance is provided on when to use this tool versus alternatives. There is no mention of when not to use it or any context for selection among sibling tools.
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.
Each tool is prefixed with its service name, and within each service, tools have distinct actions (e.g., mail_read vs. availability_find). The duvera tools cover different subdomains like dev, finance, and food with no overlap, making selection unambiguous.
All tools follow the pattern service__action_object or service__category_action, using lowercase with underscores. The order of verb and noun varies slightly (e.g., package_track vs. boardingpass_show), but the naming is highly predictable and readable.
With 52 tools, the server is large but justified as a gateway aggregating many external services. Each tool corresponds to a common task for its service, so no tool feels extraneous, though the total number is high.
The tool surface covers a wide array of services but only provides one or two basic operations per service (mostly read-only). While this suits a quick-lookup gateway, deeper workflows (e.g., creating or updating resources) are missing, leaving gaps for many use cases.
