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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds only the endpoint and category 'Despesas'; it does not disclose pagination, response shape, or filtering behavior beyond what annotations imply.

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 with the scoping category and endpoint front-loaded. It is concise and contains no filler, though it is brief to the point of omitting useful 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 two undocumented parameters and no output schema, the agent cannot understand how to filter or what the response will contain. The annotations cover safety, but the description leaves important operational context missing, so the tool is not fully usable based on the definition alone.

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 gives no hint about what 'query' or 'account' mean or how they affect the list result. Since the schema does not document the parameters and the description does not compensate, the agent has no semantic basis for using them.

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 specific verb ('Listar'), a resource ('imposto'), and the HTTP endpoint ('GET /impostos'), making the core purpose clear. However, it does not distinguish this tool from closely related siblings such as 'superlogica_despesas_list' or explain what 'impostos' means in this domain.

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 instead of other list tools, no exclusions, and no mention of prerequisites. The only signal is the HTTP GET verb, which implies a read operation but not a usage context.

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