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

Annotations already mark the operation read-only, idempotent, and non-destructive. The description adds valuable behavioral context: no credentials needed, payment via pre-paid credit, public data source, and LGPD controller obligations. Nothing contradicts the 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?

Three sentences: first gives the core action and target, the second gives operational and data-source context, the third adds LGPD responsibility. It is front-loaded and every sentence carries information, though the 'Hospedado pela plataforma' clause is minor filler.

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 description covers purpose, authentication, cost, data classification, and legal responsibility, but leaves the 'completo' parameter undefined and contains ambiguity about CPF/CNPJ being alternative vs both required. Since no output schema exists, the output is only implied by 'Emite a certidão'.

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 0% and 'completo' is not mentioned in the description. The description clarifies that CPF/CNPJ refer to person/company, but it says 'CPF ou CNPJ' while the schema requires both, and it does not explain the 'completo' boolean, formats, or optionality. Therefore the description insufficiently compensates for the lack of schema descriptions.

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 opens with a specific verb phrase 'Emite a certidão negativa de embargos ambientais do IBAMA' and identifies the target via CPF/CNPJ. It clearly differentiates from sibling tools like authenticate, connect, and marketplace, which are platform-level operations.

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?

It states the exact use case: obtaining an IBAMA environmental embargo negative certificate for a person or company. It provides clear context (public data, hosted, pre-paid credit) but does not explicitly mention exclusions or alternatives; however, sibling tools are unrelated, so no conflicting choice exists.

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