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

Annotations already cover read-only, non-destructive, and idempotent hints. The description adds valuable operational context: no platform credentials are needed, each query consumes prepaid credit, the data is officially available to citizens but not confidential, and the client bears LGPD-related responsibility. No contradiction with annotations.

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 compact four-sentence block that front-loads the purpose, then adds credential/cost context, data-source nature, and LGPD compliance. Every sentence contributes operational or compliance information; it is slightly dense but not unnecessarily verbose.

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?

With five optional parameters, no output schema, and no information about pagination, response shape, or required identifier usage, the description is not complete enough for an agent to confidently invoke the tool. The legal and payment context is useful, but the missing operational details leave a notable gap.

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 0%, and the description does not explain the five parameters (cpf, cnpj, pagina, tipo_registro, numero_registro), their expected formats, or which combinations are valid. The domain context hints that CPF and CNPJ are identifiers, but this is insufficient for a tool with five optional parameters and no required-field guidance.

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 identifies a query operation on the CFC registry of professionals and companies via the phrase 'Cadastro de Profissionais e Empresas, consulta em fonte oficial.' The verb 'consulta' and the named resource make the core purpose clear, though it does not explicitly enumerate lookup keys like CPF/CNPJ in the description.

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?

Usage is implied by the domain context: the tool is for consulting official Brazilian registry information. There is no explicit statement of when to prefer this tool over alternatives, nor exclusions; however, the legal note and mention of official sources give some contextual guidance.

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