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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral detail: pagination ('Paginado') and the meaning of detalhes.dDtConcilia (empty = pending). However it doesn't explain pagination limits or default page size.

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?

Front-loaded with purpose and use case, but the dense parenthetical enumeration of filter keys mixes reference documentation into the description. It is information-dense but somewhat crammed into a single block without clear separation between purpose, parameters, and response notes.

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?

Covers purpose, key filters, reconciliation semantics, and the dDtConcilia response field, which is substantial for a no-output-schema, 0%-coverage tool. Still missing what page/page_size/account do and any expected result shape, leaving gaps for an agent configuring the call.

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 and largely does. It documents filters JSON keys with Hungarian naming conventions (dDtPagtoDe/Ate, cTpLancamento with enum-like values 'CP','CR','BX', cStatus, nCodCC, nCodCliente), explains apenas_nao_conciliados semantics, and mentions the dDtConcilia field in responses. Page, page_size, and account parameters remain undocumented.

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?

States a specific verb+resource ('Lista movimentos financeiros — lançamentos/baixas de contas a pagar, a receber e conta corrente') and references the underlying API method ListarMovimentos. It distinguishes from omie_list_payables/omie_list_receivables by covering both plus checking account movements in a single unified listing, though it does not explicitly name the siblings.

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?

Establishes clear context: this tool is 'a base da CONCILIAÇÃO (pareia com o Banco MCP)', positioning it as the data source for reconciliation workflows. It also differentiates the apenas_nao_conciliados flag as a filter for unreconciled items. Lacks explicit when-not-to-use guidance versus omie_list_payables or omie_list_checking_account_entries.

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