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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond that: prepaid per-query billing, no platform credentials required, the data is not confidential, and the client is the LGPD data controller. No contradiction with the annotations exists.

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 front-loaded with the core purpose but contains some redundancy, such as mentioning 'consulta em fonte oficial' and later 'consulta informação de fontes e órgãos oficiais brasileiros.' The LGPD sentence is relevant context but adds length; overall it is reasonably compact but not tightly edited.

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 billing, credentials, and data sensitivity, but it is incomplete for actual invocation: it does not explain what the response contains, whether one of 'ie'/'cnpj' is required, or how the parameters are meant to be used. With no output schema and minimal parameter information, the description leaves important operational gaps.

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 input schema contains two parameters with no descriptions and 0% schema_description_coverage. The tool description does not compensate by explaining that 'ie' likely means Inscrição Estadual or how the parameters relate to each other. This is a significant gap for an agent trying to select and fill parameters correctly.

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 identifies the resource and action: consulting official SEFAZ PR sources. It distinguishes itself from generic sibling tools (authenticate, marketplace, etc.) by naming the specific government tax entity and official-source nature. However, it does not explicitly state what kind of data is returned (e.g., tax registration status), leaving slight ambiguity.

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 some usage context: no platform credentials are needed, it is a prepaid per-query service, and the data is non-confidential public information with LGPD responsibilities. However, it gives no explicit guidance on when to use this tool versus alternatives, nor does it address the choice between the 'ie' and 'cnpj' parameters.

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