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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the HTTP method and endpoint, but no additional behavioral traits such as pagination, filtering behavior, date-range handling, or authentication requirements. This is adequate but not rich.

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 compact sentence that front-loads the domain and follows with the action and endpoint. There is no redundant wording or filler. It is appropriately sized, though the brevity comes at the cost of parameter and usage 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 list tool with two optional but undocumented parameters and no output schema, the description is not complete enough for correct invocation. The agent still does not know what 'query' and 'account' expect, how results are returned, or whether results are paginated. The read-only annotations help, but they do not fill these 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?

Schema description coverage is 0%, and the description does not explain the meaning, format, or allowed values for 'query' or 'account'. Both parameters are bare strings with no required flag clarification. Since the description fails to compensate for the missing schema documentation, an agent cannot reliably construct correct arguments.

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 has a specific verb ('Listar') and a clear resource ('movimentações bancárias'), reinforced by the HTTP endpoint GET /caixa. The domain prefix 'Condomínios / Contas bancárias' adds context, and the resource differs from siblings like caixa_saldo. It clearly identifies what the tool does.

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 gives no guidance on when to use this tool versus alternatives such as superlogica_caixa_saldo, superlogica_contabancos_list, or superlogica_movimentacoesdiretas_create. There are no conditions, prerequisites, or exclusions, so the agent must infer the appropriate use case.

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