shangou_search

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

No annotations provided; description covers prerequisite but does not disclose other behavioral details like rate limits, response format, or explicit read-only nature. Adequate but incomplete.

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?

Extremely concise single sentence covering purpose, parameters, and prerequisite with no redundant 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 the tool's simplicity (2 parameters, no output schema), the description covers key aspects: purpose, parameters, and prerequisite. Lacks output format details but sufficient for agent invocation.

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%, and description adds value with keyword examples (奶茶/汉堡/超市/水果) and clarifies limit meaning. Exceeds baseline by providing concrete usage context.

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?

Description clearly states the tool searches for nearby deliverable shops/food with specific keyword examples, distinguishing it from sibling tools like shangou_shop_menu or shangou_list_addresses.

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?

Explicitly states prerequisite of being logged in and having a delivery address set, with a note on error behavior. Lacks mention of when not to use or direct alternatives.

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