Search Ninja Restaurants

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

No annotations provided, so description carries full burden. It discloses geospatial search behavior but does not mention pagination, rate limits, or authentication requirements. Adequate for a search tool but could be more specific.

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 sentences, front-loading the primary purpose and adding a workflow hint. Every word is earned, no fluff.

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?

With 11 undocumented parameters, no output schema, and no annotations, the description fails to provide sufficient context for an agent to use all features correctly. Missing details on pagination, filtering, and response format.

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 0%, yet the description only vaguely references 'saved address or coordinates' without mapping to parameters like addressId, latitude, or longitude. No explanation of other parameters (query, limit, cuisineIds, etc.), leaving the agent to guess their roles.

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 restaurant branches near a saved address or coordinates. It distinguishes from siblings like ninja_search_products and provides a workflow hint to use branchId with ninja_restaurant_menu.

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 implies usage context by mentioning a follow-up action (use branchId with ninja_restaurant_menu). It does not explicitly exclude alternatives or state when not to use, but the workflow guidance is clear enough.

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