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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds rich behavior beyond them: outdated results on mismatched cadastro/anexos/dossiê, data_atual=false for prior days, and partial batches reported via parcial=true with processados/total that never imply completion. This is substantial, non-redundant disclosure for a read tool.

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?

It is front-loaded with the core purpose and then packs edge-case semantics into short, dense sentences. Diction is jargon-heavy for a non-Portuguese reader, but each sentence carries distinct information and none is filler.

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, the description carries the return-value burden and does so: it enumerates what is returned (estado, pendências, atendidos with motivos/ações/evidências), the outdated and partial/processados/total response states, and the data_atual flag. An agent has enough to interpret results 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?

Schema description coverage is 100%, so the schema already documents all seven parameters, including enums like grupo and kind. The description adds domain meaning around the pendências categories and batch semantics, but offers little additional parameter-specific syntax, so baseline 3 is appropriate.

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 and resource ('Consulta estado, Pendências e Atendidos com motivos, ações e evidências') and, via 'Nunca inicia análise', distinguishes itself from the sibling analisar_participacao. The resource 'participacao' is domain-specific and not fully explained, but the read-vs-analyze contrast is clear.

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?

It gives strong 'when-not' guidance: 'Nunca inicia análise' and 'GET não executa a fila nem inicia IA', routing the agent away from triggering analysis. It stops short of naming the alternative tool explicitly or laying out positive preconditions, so it is clear context without full alternatives.

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