consultar_estabelecimentos_credenciados

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool performs a consultation and does not clarify whether the result is an aggregated count or a paginated list, nor does it disclose pagination, filtering behavior, or other operational characteristics.

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?

The description is a single, front-loaded sentence with no filler or redundant wording. Every part of it contributes to identifying the tool's purpose.

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 simple query tool with fully documented parameters, this reaches the minimum viability threshold. However, with no output schema or annotations, the description should more clearly state whether the tool returns a single quantity or a list of records, and it does not.

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 100%, so the baseline is 3 even though the description adds no parameter-level detail. The phrase 'por trimestre' only reinforces the trimestre parameter and does not explain top, filtro, or ordenar_por beyond what the schema already provides.

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 names a specific resource ('estabelecimentos credenciados'), a specific action ('Consulta'), and the relevant time dimension ('por trimestre'). This clearly separates it from sibling tools focused on taxas, terminais, portadores, and transações.

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 says nothing about when to use this tool versus any of its siblings, and no alternative tools are referenced. The only implicit clue is 'por trimestre', which could help distinguish it from monthly tools, but that selection logic is never stated.

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