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

Annotations already mark the tool as readOnly, idempotent, and non-destructive. The description adds valuable behavioral context beyond annotations: 'sem credenciais da plataforma' (no platform credentials needed), 'pague por consulta com crédito pré-pago' (paid per query), and 'não é dado sigiloso' (data is not confidential) plus LGPD controller responsibilities. It does not mention failure modes or output, but the annotation coverage lowers the bar.

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 and mostly efficient. It front-loads the core purpose in the first sentence. Minor redundancy exists with 'Hospedado pela plataforma, sem credenciais da plataforma', but overall it is concise and structured acceptably.

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 six undocumented parameters and no output schema, the description is not complete enough for reliable invocation. It does not explain the return format, how authentication parameters interact, or what 'situação fiscal' includes operationally. It covers commercial and legal context but lacks essential 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?

Schema description coverage is 0%, and the description does not explain any of the six parameters (login_cpf, login_senha, pkcs12_cert, pkcs12_pass, perfil_procurador_cpf, perfil_procurador_cnpj) or their relationships. Parameter names hint at meaning, but there is no guidance on required combinations or formats, so the description fails to compensate for the lack of schema descriptions.

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 the tool performs a consultation: 'consulta em fonte oficial' and 'Consulta informação de fontes e órgãos oficiais brasileiros'. It identifies the resource as Brazilian official tax situation data and is distinct from the unrelated sibling tools. However, 'situação fiscal' is somewhat broad and not precisely scoped.

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 contextual usage details: it is hosted by the platform, requires no platform credentials, costs prepaid credits per query, and involves LGPD responsibilities. It does not explicitly state when to use this tool versus alternatives or provide exclusion criteria, so guidance is implied rather than explicit.

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