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

The description discloses that the tool requires no credentials and is a paid query service, which are behavioral aspects beyond the readOnly and idempotent annotations. It also confirms that the data consulted is not confidential and clarifies data controller responsibilities, aligning with the non-destructive nature.

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 verbose, containing multiple legal disclaimers about LGPD and data control that are likely unnecessary for basic tool usage. While it is not extremely long, the extra boilerplate detracts from conciseness and could be trimmed to focus on essential operational details.

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 the lack of parameter explanations and no output schema, the description is incomplete for practical use. It provides some context about the source and payment model, but missing parameter semantics and output expectations prevent a user from effectively invoking the tool.

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?

The schema includes six parameters (cpf, cnpj, login_cpf, login_senha, pkcs12_cert, pkcs12_pass) but the description provides no explanation for any of them. Users are left to guess which parameters are required, their formats, or their purposes, making this a critical gap.

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 states the tool's function: consulting a negative tax debt certificate from the São Paulo State Attorney General's Office. It specifies the official source and includes relevant disclaimers about data handling, distinguishing it from sibling tools like authentication or reporting.

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 mentions that the service is paid with prepaid credits and is hosted on the platform, but it does not provide guidance on when to use this tool versus alternatives. There is no explicit comparison or situational advice, leaving usage context ambiguous.

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