Search & segment active Brazilian companies

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 discloses pagination (cursor), cost ($0.05/page), and data redaction (LGPD for MEI contacts). However, it omits rate limits, required authentication, and the response structure, leaving some behavioral aspects uncovered.

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?

Three well-structured sentences front-load the main action and key constraints. Every sentence adds essential information without redundancy.

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 12 parameters and no output schema, the description provides a solid overview including pagination, cost, and data handling. It could elaborate on return format or error cases, but it is largely sufficient for an experienced 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?

Schema coverage is 58% (7/12 params have descriptions). The description adds thematic grouping (industry, location, size, age, name) and clarifies that CNAE prefixes match on main activity and city can be name or code. This adds value but does not detail every parameter.

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 it searches and segments active Brazilian companies using various filters. The verb 'search & segment' plus the specific resource 'active Brazilian companies' distinguishes it from single-company lookups (lookup_company) and tender searches (search_tenders).

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 requires at least one filter and notes the paid-per-page cost, but does not explicitly state when to use this tool versus alternatives like lookup_company. However, the context signals and sibling names imply the difference, so the guidance is mostly clear.

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