baixar_fatura

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

Annotations already indicate non-read-only, idempotent, and non-destructive behavior. The description adds that it 'extracts local data,' which is vague and could imply local caching or returning parsed data, but does not explain side effects. No contradiction with annotations.

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 concise, with one main sentence and a clear recommendation. It avoids unnecessary detail and is effectively front-loaded with the primary action.

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?

While the core download action is stated, the description does not explain the output structure (despite having an output schema), nor does it clarify the role of multiple optional parameters. This leaves significant ambiguity for an agent attempting to use 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 absent, so the description must clarify parameters. It only mentions 'fatura_id' as preferred, leaving 'uc', 'conta_mes', and 'force_download' unexplained. This is insufficient given the zero coverage.

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 (download a second copy in PDF) and the resource (invoice), with a specific verb 'Baixa' and mention of PDF extraction. It distinguishes itself from the sibling list tools by focusing on a download 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 provides a direct usage hint by recommending the use of 'fatura_id' returned by listar_faturas. Although it does not explicitly contrast with sibling tools, the action of downloading versus listing makes the appropriate context clear.

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