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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: hosted platform, no credential requirement, prepaid per-query billing, official Brazilian sources, non-confidential data, and LGPD accountability. It does not mention output format or error behavior, but the added context is substantial.

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 four sentences and front-loads the core purpose in the first sentence. The following sentences add useful operational and legal context without excessive verbosity, though the LGPD sentence could be considered slightly tangential.

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 simple download-like tool, the description covers purpose, access model, data source, and legal responsibility. However, with no output schema and zero parameter descriptions, the lack of details about return format, optional credential parameters, and potential failure modes leaves 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 should compensate for all six parameters. It only clarifies the two required params ('nire' and 'registro') while leaving login_cpf, login_senha, pkcs12_cert, and pkcs12_pass unexplained. The phrase 'sem credenciais' is also ambiguous given the optional credential-like 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?

The description clearly states the action ('Baixa um documento arquivado'), the resource ('documento arquivado de uma empresa na JUCESP'), and the key identifiers ('NIRE e do número de registro'). This is specific and distinct from the sibling tools, which are mostly authentication/platform utilities.

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 clear usage context: downloads a specific archived company document from JUCESP given NIRE and registration number. It also clarifies access conditions ('sem credenciais', 'pague por consulta com crédito pré-pago') and the legal context, though it does not explicitly list exclusions or alternatives.

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