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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds only the CPF/CNPJ query scope and the 'certidão negativa' output type; it does not disclose behaviors such as what happens when debts exist or the meaning of the completo flag.

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, short, front-loaded phrase and every word adds meaning. There is no filler, repetition, or unnecessary explanation.

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?

The tool is simple and read-only, but the lack of an output schema and 0% parameter documentation leaves the agent with gaps: the meaning of 'completo', the expected return format, and any prerequisites are not described. The description is enough to identify the tool but not enough to invoke it with confidence beyond the basic ID inputs.

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?

With 0% schema-description coverage, the description must compensate but only clarifies 'por CPF/CNPJ' as the identifier scope. The boolean parameter 'completo' is completely unexplained, and there is no mention of mutual exclusivity or validation constraints between CPF and CNPJ.

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 phrase 'Certidão negativa de débitos do IBAMA por CPF/CNPJ' clearly identifies the IBAMA debt certificate and the CPF/CNPJ scope, distinguishing it from the many compliance_* sibling tools. It lacks an explicit verb such as 'retrieves' or 'consult', but the intent is still unambiguous for the domain.

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?

No explicit guidance is given about when to use this tool versus alternative compliance tools. The only clue is the IBAMA-specific scope, which requires the agent to infer selection based on the resource name.

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