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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable context beyond these: the cost model (pay-per-query with prepaid credit), the data-source nature (same data available to citizens, non-confidential), and legal responsibilities (client as data controller per LGPD). This is meaningful additional behavioral disclosure about financial and legal implications.

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?

Four sentences covering purpose, payment model, data nature, and legal compliance. It's compact but front-loads billing/legal boilerplate ('pague por consulta com crédito pré-pago', LGPD responsibilities) before the functional core. The first sentence does establish the main function, but the third and fourth sentences add legal disclaimers that feel like compliance copy rather than functional guidance.

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?

No output schema exists, and the description never addresses what the caller receives (return format, pagination, error behavior). The three parameters are wholly undocumented. For a pay-per-query tool with cost implications, the absence of any output/response description and any parameter-usage guidance leaves significant gaps. The payment context is described but the core mechanics of querying and results are not.

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 provides zero information about the three parameters (ie, cpf, cnpj). The description doesn't clarify that these are likely a one-of set (query by one identifier only), doesn't explain what 'ie' stands for (Inscrição Estadual), doesn't provide formatting guidance (masking, length), and doesn't note that none are required per the schema. No compensation for the 0% schema coverage.

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 states this is a SINTEGRA SE consultation against official Brazilian sources ('consulta em fonte oficial'). The verb 'consultar' in the name plus 'consulta' in the description makes the action clear. It doesn't explicitly contrast with sibling tools, but those (authenticate, connect, marketplace, etc.) are infrastructure tools with no apparent overlap, so differentiation isn't needed. Clear purpose, specific resource identified.

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 contextual usage information: no platform credentials needed, pay-per-query with prepaid credit, and LGPD responsibility for legitimate purpose. However, it gives no explicit when-to-use vs. when-not-to-use guidance, no mention of prerequisites, and no indication of what distinguishes this from potential alternative tax-data tools. The information present is useful but implicit rather than directive.

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