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

The annotation deststructionHint=true already indicates the tool is destructive, but the description provides no additional behavioral context such as whether importing appends to or replaces existing transactions, or what side effects might occur. The description adds no value beyond the annotation.

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 two concise sentences, front-loaded with the main purpose and followed by input format. Every word earns its place, with no unnecessary detail.

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 mutation tool with destructiveHint=true and no output schema, the description is too sparse. It does not mention return values, success/failure behavior, or any prerequisites (e.g., session must exist). The schema covers parameters, but the description leaves the agent uncertain about outcomes.

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 100%, so the baseline is 3. The description repeats what the schema already states about the array fields (data, descricao, valor, tipo), adding no additional meaning or context beyond the schema.

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 action ('imports transactions') and the target resource ('to a reconciliation session'), providing a specific verb+resource. It does not explicitly distinguish from similar sibling tools like reconciliation_import_entries, but the bank statement context adds clarity.

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 context of importing into a reconciliation session implies when to use it, but the description gives no explicit guidance on when to prefer this over alternatives like importar_transacoes or reconciliation_import_entries. No exclusions are stated.

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