Buscar un negocio por nombre o razon social

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

With no annotations provided, the description must disclose behavior on its own. It only restates the search criteria and scope; it does not mention pagination, result limits, matching behavior (exact/partial), or output structure. The schema's 'inicio' and 'fin' fields hint at pagination but the description adds no context on how results are returned or any limitations.

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?

Single sentence with no filler; the verb and target resource are front-loaded. It is appropriately sized for the content it conveys.

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?

For a tool with four parameters, no output schema, and no annotations, a one-sentence description is insufficient. It omits essential call context: how pagination parameters work, what a result record looks like, and how to refer to states. The description leaves an agent to infer too much, especially relative to the richer sibling set.

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 description coverage is 50%, leaving 'inicio' and 'fin' undocumented. The description adds no explanation for these pagination parameters and only paraphrases the existing schema descriptions for 'nombre' and 'estado'. It fails to compensate for the undocumented half of the parameters.

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 states a specific verb ('Busca') and resource ('establecimientos economicos'), with clear search dimensions: by trade name or corporate name, and geographic scope (all Mexico or a specific state). It matches the title and unambiguously differentiates from sibling tools like denue_detalle or denue_buscar_cercania by naming the resource and criteria.

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 the tool is for searching businesses by name, and mentions the optional state filter, which hints at usage. However, it never tells an agent when to prefer this over siblings like denue_buscar_por_estado, nor does it state exclusions or preconditions. The geographic note is more parameter elaboration than usage routing.

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