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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the explicit GET method and confirms a read-only listing operation, but provides no extra behavioral context such as pagination, authentication, or data scope. There is no contradiction with the 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?

The description is a single concise sentence with the endpoint front-loaded and no filler. It is appropriately compact for a simple list operation, though the brevity contributes to missing parameter context.

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?

With no output schema and zero parameter descriptions, this one-liner is incomplete for invocation. It does not explain what 'query' and 'account' mean, what the response contains, or what selection criteria apply, so an agent cannot fully rely on it beyond knowing it is a safe read operation.

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 says nothing about the two parameters, 'query' and 'account'. Neither the schema nor the description explains their format, meaning, or optionality, leaving an agent unable to construct valid arguments confidently.

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 explicit verb 'Listar' and names the resource 'condôminos' with the endpoint GET /responsaveis/index, making the tool's basic purpose clear. It does not explicitly differentiate itself from sibling list tools such as superlogica_tickets_list or superlogica_sindicos_list, so it misses the top score.

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 rather than one of the many sibling list tools. The description only states the action and endpoint; it provides no use-case context, exclusions, or alternative tool references.

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