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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds source context ('Portal do Parceiro') and scope ('da loja'), but does not disclose behaviors like pagination, ordering, or date range. This is acceptable given the simple list operation, but not beyond what annotations cover.

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 that clearly states what the tool does without any filler. It is well-structured and immediately readable.

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 simple tool with no parameters and read-only annotations, the description is mostly sufficient. It explains the domain and source. However, since there is no output schema, a brief mention of the return format (e.g., a list of entries) would improve completeness, but it is not critical.

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?

There are zero parameters, so the schema is trivially fully covered. The baseline for zero parameters is 4; the description does not need to explain parameters, and it correctly focuses on the tool's purpose.

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 'Lista' (lists) and identifies the resource as 'lançamentos financeiros / repasses da loja no iFood' (financial entries/pass-throughs of the store on iFood). It also adds context that this is the financial statement from the Partner Portal, clearly distinguishing it from sibling tools like ifood_vendas_financeiro_resumo.

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 when one needs to list financial entries/repasses, but it does not explicitly mention alternatives or when not to use this tool. Sibling tools such as financeiro_resumo exist, but no differentiation guidance is provided.

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