obter_boleto

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action of obtaining a link, but does not mention side effects (e.g., read-only nature), authentication requirements, or behavior when the title is not found. This minimal disclosure leaves important behavioral aspects opaque.

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 is front-loaded with the primary verb and object. It contains no filler or redundant content, making it efficient and easy to parse.

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 lack of annotations and output schema, the description must provide comprehensive guidance. It states the return is a download link, which is helpful, but it fails to explain the input parameters or the distinction between the two optional identifiers. For an agent to correctly invoke the tool, it needs to know how to specify the título, which is absent.

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?

The schema description coverage is 0%, and the description does not mention the parameters at all. Both 'codigo_titulo' and 'codigo_titulo_integracao' are optional and nullable, but the description fails to explain how they identify the título, their relationship, or which to use. The description adds no value in clarifying parameter usage.

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 tool's function with a specific verb ('Obtém') and resource ('link de download do boleto de um título já gerado'). It distinguishes itself from sibling tools like 'gerar_boleto' and 'cancelar_boleto' by focusing on retrieval of an existing boleto's download link.

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 phrase 'já gerado' implies the prerequisite that the title must already exist and that this tool is not for generating new boletos. However, it does not explicitly state when to use it versus alternatives, nor does it mention exclusions (e.g., do not use before generation).

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