buscar_credor

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals an important behavior beyond searching: it validates the check digit before executing the search and treats invalid CNPJ as a likely photo-reading error. The read-only nature is implied by 'Busca' but not explicitly stated.

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 two concise sentences with information front-loaded: first the core search purpose, then the validation behavior and fallback action. There is no filler or redundant restatement.

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 search tool with no output schema, the description covers what it searches, by which identifiers, and what to do when validation fails. It could more explicitly state that at least one identifier parameter should be provided, but overall the operational guidance is strong.

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 100%, with each parameter already described as 'com ou sem máscara.' The description adds a small behavioral note about CNPJ validation, but it does not substantially expand on the schema's parameter definitions. Baseline 3 is appropriate given the high schema coverage.

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 uses a specific verb and resource: 'Busca o fornecedor (credor) no Sienge por CNPJ, CPF ou nome.' It clearly identifies the system, the entity being searched, and the available search keys. This makes it easy to distinguish from siblings like buscar_titulos or criar_credor.

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 gives clear context for when to use the tool and even provides a workflow for invalid CNPJ input: check the photo or ask the user for the number. It does not explicitly compare against alternatives such as criar_credor or verificar_documento, so it stops short of full exclusion guidance.

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