search_shop

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

No annotations are provided, and the one-sentence description discloses no behavioral traits such as authentication requirements, rate limits, sorting behavior, pagination, or return format. For a search tool with zero annotation coverage, this is a significant gap.

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 front-loaded and has no wasted words, but it is under-specified for a tool with six parameters and no schema descriptions. Brevity here comes at the cost of necessary information.

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 six parameters, no annotations, no output schema, and no parameter documentation, the description is far too sparse. An agent cannot reliably invoke this tool or understand its options from the description alone.

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 input schema has six parameters with 0% description coverage, and the description does not mention any of them. Parameters like sort, filter, exclude, start, and display are left completely unexplained, forcing the agent to guess their meaning and usage.

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 specific verb and resource: 'Search shopping items.' It is distinguishable from sibling searches like search_blog or search_news by the shopping domain, though it does not explicitly reference those alternatives.

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?

There is no guidance on when to use this tool versus the many sibling search tools, nor are there any exclusions or prerequisites. Usage is only implied by the shopping-specific resource name.

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