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

Annotations already cover read-only, idempotent, and non-destructive. The description adds valuable behavioral context: payment model, lack of user credentials, sourcing from official government bodies, and LGPD data controller responsibility. 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?

Four concise sentences, each conveying essential information (purpose, hosting/payment, data source, legal responsibility). No fluff, well-structured.

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?

For a tool with 7 parameters and no output schema, the description covers the core use case but omits clarification for credential-related parameters and their optionality, leaving potential confusion. It also doesn't explain the certificate format or detail any response behavior, but that's not strictly required given no output schema.

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 coverage is 0%. Description mentions cnpj, nire, and name as identifiers, but leaves login_cpf, login_senha, pkcs12_cert, and pkcs12_pass unexplained. Also, saying 'sem credenciais' conflicts with the existence of credential parameters, creating ambiguity. The description fails to clarify these parameters.

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?

Description clearly states it issues a simplified business certificate from JUCESP, specifying the resources (CNPJ, NIRE, or name). It's distinct from sibling tools which are platform utilities like authentication and 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?

Provides clear context: hosted platform, no credentials needed, prepaid credits required, and it queries official public data. It implies when to use (for obtaining registration/status proof) but doesn't explicitly state when not to use or alternative tools, though siblings are unrelated.

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