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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful context about official data sources, non-confidentiality, and LGPD responsibility. However, the claim 'sem credenciais' is ambiguous given the credential-related parameters in the schema, and no rate limits or response behavior are disclosed.

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 three sentences, front-loaded with the core purpose, then access/cost, then legal context. It is concise and contains no filler, though the LGPD sentence is somewhat tangential to tool invocation.

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?

It covers purpose, data source, cost, and legal responsibility, and implies return content (registro, situação, histórico). However, with no output schema and 7 parameters, the lack of response-shape details and the unaddressed credential parameters leave meaningful 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?

Schema description coverage is 0%, so the description must compensate. It maps cnpj, nire, and name to the stated search identifiers, but it completely ignores login_cpf, login_senha, pkcs12_cert, and pkcs12_pass, leaving 4 of 7 parameters unexplained. The 'sem credenciais' statement also conflicts with the presence of these credential fields.

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 a specific query operation: retrieving a complete JUCESP company registration record, including status and history, by CNPJ, NIRE, or name. This distinguishes it from the unrelated sibling tools and states the resource and scope precisely.

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 provides clear operational context: the tool is platform-hosted, requires no credentials, and is paid per query with prepaid credit. It does not explicitly name alternatives or exclusions, but the sibling tools are unrelated, so the context is sufficient for an agent to know when this tool applies.

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