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

Annotations already declare readOnly and idempotent hints, so the description need not repeat them. It adds a pagination behavior note ('pagine com pagina/quantidade_registros'), which is useful. However, it does not disclose any other behavioral traits such as default page size or filtering capabilities.

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 that packs the purpose, endpoint, and pagination guidance without superfluous content. It is efficiently written, though it could include more detail without becoming verbose.

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?

Given the presence of a nested 'filtro' object and no output schema, the description is insufficient. It does not explain how to construct a valid filter or what results to expect, and lacks enough detail to guide an agent in a complex search. The vague 'critérios conforme a API' placeholder does not offer practical assistance.

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?

With schema description coverage at 0%, the description must compensate. It explains that 'filtro' holds API criteria and that 'pagina' and 'quantidade_registros' are for pagination. While this adds some meaning, it is vague and does not detail the structure of the filter object or parameter constraints.

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 clearly states it is a financial search for revenues and expenses ('Busca Financeiro: receitas e despesas') with a filter, and indicates the HTTP endpoint. It distinguishes from other consulta tools by its target entity (receita_despesa), but does not explicitly contrast with 'projuris_get_receita_despesa' which likely fetches a single record.

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 description implies this tool is for searching with filters and pagination, but it does not explicitly state when to use this tool versus the 'get_receita_despesa' sibling or other consulta tools. Pagination guidance is given, but no exclusions or alternative recommendations are provided.

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