baixar_processo

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

With no annotations, the description carries the transparency burden. It discloses the key behavior that the tool downloads an integral PDF assembled by the system, which is useful context. However, it does not mention permissions, potential errors, or side effects, though for a download operation this is acceptable.

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, concise sentence that front-loads the action ('Baixa o PDF integral') and includes all essential information without any filler. It is easy to parse and well-structured.

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 tool with two parameters and an output schema, the description is fairly complete. It explains the output (PDF), destination, and full-process scope. It does not detail error handling or how to obtain the process ID, but these are not critical for using the tool correctly.

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 descriptions are missing (coverage 0%), so the description must compensate. It adds meaning to 'pasta' (indicated folder) through 'para a pasta indicada', but 'id_processo' is only implied via 'do processo' and its name. The description partially clarifies parameters but not fully.

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 that the tool downloads the full PDF of a SPA-PMT process, including all parts in a single file, to a specified folder. The verb 'Baixa' and resource 'processo do SPA-PMT' are specific, and it distinguishes itself from sibling tools like 'baixar_documento_judicial' which handles individual judicial documents.

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 the tool is used when a user needs the complete process PDF, as opposed to individual document downloads or process lookup. It provides clear context but does not explicitly mention when not to use it or name alternative tools.

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