listar_titulos_tesouro

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

With no annotations, the description carries the burden of behavioral disclosure. It makes clear this is a read-only listing of available securities and states the data scope (latest rate and price), which is useful. It does not mention output shape, pagination, data source, or refresh behavior, but for a simple no-parameter listing tool the core behavior is reasonably transparent.

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?

One compact sentence, front-loaded with the action, and no filler. The qualifiers 'disponíveis' and 'mais recentes' carry useful meaning without adding unnecessary length.

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 no-parameter listing tool, the description covers purpose and core output contents. However, because there is no output schema or annotations, and the description does not distinguish this tool from get_titulo_tesouro or state any usage conditions, the overall context is adequate but not complete.

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 tool has zero parameters and 100% schema coverage, so there is nothing for the description to add. Per the zero-parameter baseline, this 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 uses a specific verb ('Lista') and resource ('títulos do Tesouro Direto disponíveis') and adds the key content of the returned data ('taxa e preço mais recentes'). It is clear, though it does not explicitly contrast with the sibling get_titulo_tesouro, so some differentiation is left to the name.

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?

No guidance is given on when to use this tool instead of alternatives such as get_titulo_tesouro or simular_tesouro. The intended use is only implied by the tool's name and purpose; there are no explicit conditions, exclusions, or preferred scenarios.

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