consultar_conta_corrente

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

With no annotations provided, the description must disclose behavioral traits, but it only states the query action. It does not mention whether the operation is read-only, whether exactly one of the two identifier parameters must be provided, what happens if both are omitted, or any error conditions.

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, direct sentence with no filler or repetition. It is efficiently structured, though minimal in content; conciseness is appropriate but not exceptional.

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 query tool with two optional parameters, no output schema, and no annotations, the description is too sparse. It fails to explain how to identify the account, what 'detalhes' includes, or the expected response shape, leaving significant gaps for the agent.

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 description coverage is 0%, and the description adds no meaning to the two parameters (codigo_integracao and codigo_conta_corrente). It does not explain that either identifier can be used, their relationship, or which one is preferred.

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 'Consulta' and resource 'detalhes de uma conta corrente específica', clearly indicating it queries details of a single current account. The word 'específica' differentiates it from sibling list tools like 'listar_contas_correntes'.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention that listar_contas_correntes should be used for listing multiple accounts, nor does it clarify that this tool is for retrieving details given a specific account identifier.

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