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

While the description mentions the data is from an official public source, is not confidential, and is subject to LGPD and customer liability, it does not explain the tool's behavior when the resource is not found, the query returns zero results, or the API call fails. It also doesn't clarify whether the 'ie' must be a Sefaz-specific state inscription or if it accepts other identifiers.

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 block of text with no sectioning, examples, or structured hints. It is not concise in a helpful way—it is verbose about the data source and LGPD but omits critical operational details. The LGPD and data-source information, while relevant, should be secondary to guidance on how to structure a query.

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?

Given this is a read-only query tool with multiple identifier parameters and no output schema, the description needed to explain how to execute a valid query, what the response format is, and how to handle common errors. The focus on data source and LGPD compliance, while important, does not make the tool's usage clear. The lack of examples or parameter relationships is a significant 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?

With 0% schema description coverage, this description is the only source of parameter meaning. It fails to explain that 'ie' is the Sefaz-specific state registration number, nor does it clarify how the CPF and CNPJ parameters map to the query. The names are labels, not explanations, making it impossible to use this field correctly in most cases.

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 identifies the resource as 'SEFAZ PE: Certidão de Regularidade Fiscal' and notes it is a 'consulta em fonte oficial', but it fails to specify the exact verb (what operation is performed) or the specific data resource (the Sefaz RS vehicle registration system). This is vague, especially when compared to the clarity available in sibling tools.

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 provides no guidance on when to use this tool over alternatives or how to handle the three identifier parameters (ie, cpf, cnpj). It is unclear whether only one is required, how they interact, or whether to prioritize the 'ie' for Sefaz-specific queries versus the CPF/CNPJ.

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