preparar_download_pjedocs

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

No annotations are provided, so the description must carry the full burden. It discloses that generation is not triggered, but says nothing about side effects, permissions, error conditions, or what happens on success or failure. The behavioral disclosure is minimal and does not go beyond the obvious.

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, tight sentence with no wasted words. It front-loads the action and the key qualifier ('sem disparar a geração') is placed immediately. Perfectly concise.

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 that this tool is part of a download workflow with siblings like 'solicitar_download_pjedocs' and 'baixar_resultado_pjedocs', the description lacks essential context: when to use it (before triggering generation), what it returns (though an output schema exists), and any preconditions. The description is too thin for an agent to correctly sequence it.

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% (no descriptions on parameters). The description does not explain the meaning or format of 'numero' or 'grau'. While the names are somewhat self-explanatory, the description adds no semantic value and fails to compensate for the missing schema documentation.

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 clear verb ('Prepara'), a specific resource ('a solicitação da íntegra no PJeDocs'), and explicitly notes it does not trigger generation, distinguishing it from sibling 'solicitar_download_pjedocs'. This is specific and unambiguous.

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 implies a workflow distinction by saying 'sem disparar a geração', but it does not explicitly state when to use this tool versus alternatives, nor any preconditions or sequencing. No mention of when-not-to-use or recommended context.

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