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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's explicit 'GET' method is consistent with that safety profile, adding a concrete behavioral detail. However, it discloses nothing about pagination, filtering semantics, error behavior, or authentication, so beyond the endpoint and domain context it adds limited behavioral information. No contradiction with annotations.

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?

A single front-loaded sentence that immediately states the verb, resource, domain scope, and endpoint with zero filler. Every element earns its place and there is no 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?

This is a simple read-only list operation with two optional parameters and no output schema. The description covers purpose and endpoint, and annotations cover the safety profile, but the meanings of query/account and the response shape remain undocumented. It is adequate for the simple case but has clear 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%, so neither 'query' nor 'account' has an inline description, and the description text does not explain either parameter. The names are suggestive but ambiguous ('query' could mean search text or query parameters; 'account' is undefined). Because the description needed to compensate for the 0% coverage and did not, this dimension scores low.

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 names a specific verb ('Listar') and resource ('formas de pagamento'), and even includes the HTTP endpoint (GET /formasdepagamento), making the operation unambiguous. The 'Condomínios:' prefix scopes the domain. However, it does not explicitly differentiate this tool from sibling list tools (e.g., superlogica_cobranca_list), even though no sibling appears to duplicate the payment-methods resource.

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?

There is no guidance about when to use this tool versus alternatives, no exclusions, and no prerequisites or context conditions. The 'Condomínios:' prefix implies a domain scope but does not explain selection criteria or when another list tool would be more appropriate.

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