Search Ninja Products

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

No annotations provided, so description must disclose behavioral traits. It only says it searches and returns specific fields, but omits side effects, required permissions, pagination behavior, or error conditions. This is insufficient for a tool with 9 parameters.

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?

Two sentences with no redundancy, but the first sentence could be more informative about parameter usage. It is acceptably concise but misses opportunities to add value.

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 the tool's complexity (9 parameters, no output schema, no annotations), the description is severely incomplete. It fails to explain how to construct a search, interpret results beyond two fields, or handle errors. A complete description would provide parameter semantics and usage context.

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 has 9 parameters with 0% description coverage, yet the description explains none of them. It does not elaborate on query, limit, latitude, longitude, addressId, brandCode, productIds, or categoryIds. The vertical parameter is implied but not explicitly linked to the three categories listed.

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 retail, pharmacy, or beauty products using a named endpoint, specifying returned fields imageUrls and orderItemId/productId. This is a specific verb-resource combination and distinguishes from sibling tools like ninja_discover_retail_context and ninja_search_restaurants.

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 on when to use this tool versus alternatives like ninja_discover_vertical_context or ninja_search_restaurants. No mention of prerequisites, limitations, or preferred scenarios.

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