now_search

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that results are restricted to products deliverable to the account's current address, that multiple items should be batched into one call, and it enumerates the returned fields. It omits result pagination behavior, behavior on zero matches, and whether sponsored results are always interleaved.

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?

Three compact sentences, front-loaded with the action and batching rule, followed by the deliverability constraint and the return shape. Every clause carries information and none of it restates the tool name.

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 two-parameter search tool with no output schema, the field enumeration substitutes well for a return-value spec, and the address-scoping caveat covers the main surprise an agent could hit. What is missing is guidance on choosing this over the sibling lookup tools and what an empty result set means.

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%, with the queries and limit parameters fully documented in the schema itself, so baseline is 3. The description reinforces the array semantics ("one call for the whole list") but adds nothing about limit tuning or query phrasing beyond the schema's own example.

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 gives a specific verb and resource ("Search Amazon Now") plus the batching scope ("one or more items (one call for the whole list)"), which separates it from single-item operations. It never names a sibling tool, so the differentiation from now_add_items or now_get_pantry is left implicit.

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?

Usage is only implied by the shopping flow: you search to discover products, presumably before adding them to the cart. There is no explicit "use this when..." statement, no exclusion of the other lookup siblings, and no note that now_get_pantry is the better route for reordering known items.

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