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

Annotations mark destructiveHint: true, but the description does not disclose what destructive action occurs (e.g., overwriting existing entries). It only says 'imports' without clarifying side effects, leaving a significant gap for a potentially destructive 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?

Two concise sentences, front-loaded with the purpose, no superfluous content.

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?

While the schema is rich, the description lacks context about the destructive potential (from annotation) and does not differentiate from the sibling reconciliation_import_transactions. It also does not mention what the tool returns or the effect on the session, leaving the agent somewhat in the dark for a complex import operation.

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 baseline is 3. The description summarizes the array fields (data, descrição, valor, tipo, contas débito/crédito) but omits optional fields like documento, historico, favorecido, which could mislead. It does not add meaningful detail 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 tool imports general ledger entries ('lançamentos do razão contábil') into a reconciliation session, using a specific verb and resource. It distinguishes from siblings by focusing on accounting entries rather than transactions.

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?

Provides clear context for when to use: to import ledger entries into a reconciliation session. However, it does not explicitly mention alternatives or when not to use, such as the difference from reconciliation_import_transactions.

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