baixar_documento

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

The description reveals a meaningful behavioral trait: it preserves the original file when available. However, with no annotations, it does not disclose authentication needs, error behaviors, or side effects. The single nuance is helpful but incomplete for a tool operating on legal documents.

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 sentence that conveys purpose and a key behavior. It is concise and free of filler, earning every word.

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 four parameters, no annotations, and no output schema, the description is too sparse. It does not cover authentication requirements, output format, or the meaning of parameters, making it insufficient for an agent to use the tool confidently in real scenarios.

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% and the description mentions no parameter names or meanings. The required parameters (numero_processo, grau, documento_id) are undocumented, and the optional diretorio_destino is not explained. The description's reference to 'processo' and 'documento' provides only general context, not parameter-level semantics.

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') and the resource ('documento acessível do processo'), and adds a distinguishing detail about preserving the original file. It is specific enough to differentiate from siblings like baixar_inteiro_teor, though it does not explicitly name alternatives.

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?

There is no guidance on when to use this tool versus siblings such as listar_documentos or baixar_inteiro_teor. The description does not mention prerequisites like authentication, which is a notable omission given the sibling tool autenticar.

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