consultar_lancamento_bancario

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

No annotations are provided, and the description only says 'consulta,' implying a read operation. It does not disclose required parameters, error behavior, or return format, which are critical for a tool with no structured 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 a single, front-loaded sentence that is efficient and free of redundancy. It does not waste words, though it could be more informative without adding bulk.

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?

With two parameters, no parameter descriptions, no output schema, and no annotations, the one-sentence description is inadequate for reliable tool selection and invocation. It lacks context about return values and parameter semantics.

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 coverage is 0%, and the description does not mention codigo_lancamento or codigo_lancamento_integracao at all. The agent gets no explanation of what these identifiers mean, whether they are mutually exclusive, or which one is needed.

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 it consults details of a specific bank transaction ('Consulta detalhes de um lançamento bancário específico'), using a specific verb and resource. It distinguishes from sibling 'listar_lancamentos_bancarios' by emphasizing 'específico' (specific).

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 provided on when to use this tool versus alternatives like listar_lancamentos_bancarios or pesquisar_lancamentos_financeiros. It does not mention which parameter to prefer or whether the two codes are alternatives.

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