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

Annotations already indicate read-only, idempotent, non-destructive. The description adds value by noting payment per query, that no platform credentials are needed, and that data is non-confidential from official sources. It also mentions LGPD compliance. However, it lacks detail on failure modes, such as what happens with an invalid order number, or authentication requirements for the registry. This is moderate transparency beyond 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 a single paragraph of moderate length. It front-loads the core action ('Download de Certidão Digital') but then veers into legal and hosting details. The structure is not organized with bullet points or clear separation of key info. It's acceptable but not optimally concise or front-loaded.

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?

Given the tool's complexity (6 parameters, all undocumented), the description is incomplete. It does not explain parameter roles, expected inputs, or return values. No output schema is present, but the description also omits mention of what the user receives (e.g., a file, a confirmation). The payment model and data source are helpful, but they don't compensate for the missing operational details.

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?

With schema description coverage at 0%, the description must explain parameters. It does not mention any of the six parameters (email, senha, tipo_login, pkcs12_cert, pkcs12_pass, numero_pedido) by name or role. The phrase 'sem credenciais da plataforma' hints that email/senha are not platform credentials, but this is vague and doesn't clarify their purpose. No parameter semantics are provided.

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 a specific verb+resource: 'Download de Certidão Digital' (download digital certificate) and mentions 'consulta em fonte oficial' (query in official source). This clearly conveys the primary functionressed in the tool name. However, it does not explicitly differentiate from sibling tools (e.g., authenticate, connect) beyond the certificate domain, so it misses full sibling differentiation.

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 context about payment (prepaid credit) and lack of platform credentials but does not offer explicit when-to-use guidance or contrast with alternatives. It fails to specify scenarios like 'use this to retrieve a certificate after issuance' or exclusions (e.g., do not use for other queries). The guidance is implicit at best.

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