match_business

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

Discloses return behavior (ranked candidates, first is best match, empty list on no match) beyond what annotations provide. Annotations (readOnlyHint, idempotentHint) already indicate safety; description adds matching details.

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?

5 sentences, front-loaded with purpose, well-structured. Could be slightly more concise but no waste. Effective for an AI agent.

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?

Covers purpose, usage, parameters, and return format. Output schema exists but is not explained in description; however, the description mentions enrichment fields (Yelp ID, rating, etc.) which is sufficient for an AI agent.

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?

Description adds semantic context beyond input schema, e.g., 'significantly improves match precision' for zip_code/phone, and explains match_threshold values. Schema coverage is 0% but description compensates well.

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 matches a business by name/address to its canonical Yelp listing, differentiating it from siblings like find_business_by_phone and search_businesses.

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 when to use (structured address data for verification/enrichment) and describes required vs optional parameters. Could be improved by contrasting with sibling tools, but still clear.

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