Exportar cálculo do PJe-Calc (.PJC)

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

The annotations already declare that this is a non-read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds useful behavioral context beyond the annotations by specifying that the output is an actual .PJC file and explaining the intended workflows, though it does not disclose overwrite behavior or permission requirements.

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?

A single, front-loaded sentence that leads with the verb and resource, then adds the UI path and use cases without redundancy. Every clause earns its place.

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 low complexity, complete schema coverage, and annotations that cover the mutation and safety profile, the description is nearly complete for correct invocation. It omits only minor details such as overwrite behavior and what the tool returns, which is a small gap for a file-export operation with no output schema.

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 100%, and the schema already explains both parameters, including the default destination folder and the meaning of id_calculo. The description does not add any parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 (Exporta), a specific resource (um cálculo do PJe-Calc), and a specific output format (.PJC), while also naming the UI path (Operações > Exportar). It clearly distinguishes itself from the sibling calculo_ler_pjc, which performs the inverse read operation.

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?

It explicitly states three concrete use cases: backup, sending to third parties, and checking against calculo_ler_pjc. However, it does not state when not to use the tool or present a full alternative decision rule, keeping it just short of a 5.

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