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 description is not the sole source of safety information. It reinforces read-only behavior through 'Obter' and 'GET', but adds little beyond the annotations and does not disclose error behavior, authentication needs, or response characteristics.

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 phrase that leads with the domain, states the action and resource, and includes the endpoint. Every part contributes useful information, with no filler or redundancy.

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 tool with no output schema and undocumented parameters, the description is too thin: the agent cannot determine accepted values for 'query' and 'account', how to select a specific account, or what the result looks like. The read-only annotations reduce safety concerns but not the operational ambiguity.

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 'query' or 'account' parameters. The phrase 'conta bancária' gives some context for 'account', but 'query' remains undefined, and the description adds almost no parameter-level meaning beyond the parameter names.

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 states a clear action and resource: 'Obter saldo de conta bancária' (get bank account balance), scoped to 'Condomínios / Contas bancárias', with the endpoint GET /caixa/saldo. It does not explicitly distinguish itself from sibling tools such as superlogica_caixa_list or superlogica_contabancos_list, so it stops short of a 5.

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?

No guidance is provided about when to use this tool instead of related account/balance tools, nor are prerequisites, exclusions, or alternatives mentioned. The domain label and GET endpoint imply a read-only balance lookup, but the agent is left to infer the appropriate invocation context.

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