dianping_search

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

No annotations are provided, so the description carries the full burden. It only states it searches merchants and mentions city for logging, but does not disclose any behavioral traits such as whether it is read-only, pagination, rate limits, or authentication requirements.

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 very concise with two short sentences. However, the second sentence about the city parameter could be better integrated. It front-loads the purpose but could be more structured.

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 that an output schema exists, the description need not explain return values, but it omits any mention of the required keyword parameter, which is essential for use. The description only addresses one of three parameters, making it incomplete for an agent to effectively use the tool.

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 schema has 0% description coverage for parameters. The description explains the city parameter ('used to record the search city for the agent') but does not explain the required keyword parameter or the limit parameter, which are left to the schema alone.

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 'search Dianping merchants' which is a clear verb+resource. It distinguishes from sibling tools like dianping_reviews and dianping_shop by specifying 'merchants'. However, it does not explicitly differentiate from other platform search tools, but the tool name itself provides that context.

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 alternatives like dianping_shop or dianping_reviews. The description only explains the city parameter, not when to invoke the tool.

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