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

Annotations already mark it read-only, idempotent, and non-destructive. The description adds useful behavioral context: default fase (pagamento), returned fields, and federal-only scope. It does not contradict the annotations, though it omits pagination/ordering behavior.

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?

Two dense, well-structured sentences front-load the core purpose and return fields, then end with an alternative-tool pointer. No unnecessary repetition or 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?

For a 5-parameter tool with no output schema, it covers scope, return fields, default phase, and sibling differentiation. However, parameter semantics are incomplete and it lacks details on pagination/ordering/output structure, leaving meaningful gaps for autonomous invocation.

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 0% schema description coverage, the description carries the burden but only partially covers parameters. It explains `fase` values and implies `ano`, but omits `pagina`, `ordenacao`, and CPF/CNPJ format. Additionally, 'fase default = 3' conflicts with the schema's string enum, causing ambiguity.

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 lists item-level expense documents (Empenho, Liquidação, Pagamento) for a beneficiary, with a specific field list. It also explicitly contrasts itself with the sibling tool `transparencia_despesas_favorecido`, distinguishing its granular, item-level purpose.

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 says when to use this tool (item-level federal expense documents) and provides an explicit alternative for aggregate totals. The 'Só Executivo FEDERAL' scope further clarifies limitations, giving clear context and exclusions.

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