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

The annotation destructiveHint: true already informs the agent the operation is destructive, and the description does not contradict it. However, the description adds little behavioral context beyond the batch aspect, such as whether the import appends, overwrites, or has validation side effects.

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 states the action and then lists required fields. It is compact and avoids fluff, conveying essential information efficiently.

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?

The tool has a rich schema and a destructive annotation, but the description lacks details about the meaning of empresaId (especially default 0), the optionality of categoriaId, and any side effects of bulk import. The description provides a minimal summary but leaves these contextual gaps.

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?

Although schema coverage is 100%, the description lists categoriaId as a required field ('deve ter') while the schema marks it optional, creating a contradiction. This misinformation reduces the added value, and the description otherwise only repeats field names without enriching 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 tool imports financial transactions in bulk for a company, using the specific verb 'Importa' and a distinct resource. This distinguishes it from sibling tools like classificar_transacao and listar_transacoes, which handle classification and listing.

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 usage for bulk importing transactions through its 'em lote' phrasing, but it does not explicitly state when to prefer this tool over alternatives, nor does it mention any prerequisites or exclusions. For example, it doesn't clarify when to use this vs reconciliation_import_transactions.

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