incluir_conta_corrente

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool creates a new account, without mentioning side effects, permissions, validation rules, response format, or error behavior. This is a significant gap for a creation operation.

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 with no wasted words. It front-loads the action ('Cadastra') and the object ('nova conta corrente/bancária'). However, it is extremely brief, which borders on under-specification rather than effective conciseness.

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 tool's complexity (12 parameters, 2 required, no annotations, no output schema), the one-sentence description is wholly inadequate. It fails to explain required fields, parameter semantics, expected response, or any operational context needed for correct invocation.

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%, so the description must compensate by explaining parameters. However, the description does not mention any of the 12 parameters, their meanings, or how they relate to the creation process. The parameter names are not self-explanatory beyond basic Portuguese, and no additional semantics are provided.

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 the specific verb 'Cadastra' (registers/creates) and clearly identifies the resource as 'nova conta corrente/bancária' (new current/bank account). This distinguishes it from sibling tools like alterar_conta_corrente (update), excluir_conta_corrente (delete), and listar_contas_correntes (list).

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 implies the tool is for creating a new bank account, but it does not explicitly state when to use it over alternatives or provide exclusions. Since the verb and resource clearly indicate the creation use case, usage is implied rather than explicitly guided.

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