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

Annotations indicate read‑only, idempotent, non‑destructive operationches; the description adds further useful information: payment model, lack of credentials, and LGPC responsibility. This goes beyond the annotations, though it does not specify response format or error behavior. No contradiction with annotations.

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 concise and front‑loaded with the purpose, then states payment and data source. It is not overly long and is easy to parse.

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 tool has multiple parameters and no output schema. The description gives the core purpose and cost model but omits clarification about the authentication parameters and the expected response. Since it is a simple query tool the idea is clear, but the missing parameter explanations reduce completeness.

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 description clarifies that queries can be made by CNPJ, NIRE, or name, covering three of seven parameters. However, the authentication parameters (login_cpf, login_senha, pkcs12_cert, pkcs12_pass) are not mentioned at all, and the schema provides no descriptions (coverage 0%). The description fails to explain these parameters or whether they are required, leaving the agent with insufficient guidance.

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 this tool retrieves a simplified corporate registration record (ficha cadastral) from JUCESP, specifying the query keys (CNPJ, NIRE, or name). This distinguishes it from the sibling tools, which are unrelated (authentication, marketplace, version info).

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 explains the general context: hosted by the platform, no credentials required, prepaid credits per query. It also indicates the data source is official Brazilian records. However, it does not explicitly state when to prefer this tool over alternatives (though no alternatives exist among siblings) nor when not to use it.

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