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 well covered. The description adds the explicit GET endpoint and the agreement-generation context, which is useful, but it does not disclose response shape, pagination, or authentication requirements. This is adequate given the strong 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, and the key action 'Listar inadimplência de uma unidade' is front-loaded. The navigational breadcrumb prefix is slightly extraneous but the overall structure wastes little space.

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 two undocumented optional parameters and no output schema, the description should at least define the inputs or the intended unit scope. It does not explain what to pass for 'query' or 'account', and it leaves the relationship to 'superlogica_inadimplencia_list_get' unresolved. The annotations cover safety but not how to invoke the tool correctly.

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?

The schema has two string parameters, 'query' and 'account', with 0% schema description coverage, so the description must compensate for their meaning. It does not explain what value each parameter expects or how they map to the 'unidade' mentioned in the description, leaving the agent to guess.

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: 'Listar inadimplência de uma unidade' (list a unit's delinquency) and even includes the HTTP endpoint GET /inadimplencia. However, it does not distinguish this tool from the similarly named sibling 'superlogica_inadimplencia_list_get', so it falls just 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?

The breadcrumb 'Receitas / Acordos / Obtendo dados para gerar o acordo' implies this is used when collecting data to generate an agreement, but there is no explicit when-to-use or when-not-to-use guidance. It also does not mention alternatives or clarify how it differs from the nearly identical sibling tool name.

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