search_businesses

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

With no annotations, the description must carry full weight. It adds important transparency about output features (fit_score, trust_score, risks, sources) and warns against inventing data, but does not explicitly state that the tool is read-only or non-destructive.

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?

Concise and well-structured with no unnecessary words. Purpose, usage, parameters, and warnings are all front-loaded in a few sentences.

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 simple input schema (2 parameters, no output schema), the description provides sufficient context: expected output (ranked businesses with scores, sources), usage examples, and a warning about data provenance.

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 description explains both parameters ('intent: a intenção em linguagem natural' and 'limit: número máximo de resultados') beyond the schema definitions, which only provide type and default values.

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 for real, verifiable businesses using natural language intent ('Busca empresas reais e verificáveis por uma intenção em linguagem natural'). It distinguishes from the sibling tool (get_business_profile) which is for retrieving individual business profiles.

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?

Provides clear usage context with examples ('Use quando o usuário quiser encontrar um negócio (ex.: farmácia em Copacabana...)') but does not explicitly exclude scenarios or mention alternatives beyond the sibling tool.

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