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

Beyond the read-only/idempotent annotations, the description discloses that it triggers no processing, that stale company/attachment/dossier inputs return outdated, the reference-date behavior (data_atual=false for a previous day), and that validated batches surface as parcial=true with processados/total without meaning pending requirements are done. This is substantial behavioral context an agent could not derive from annotations or schema.

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 what-it-does sentence is front-loaded and each subsequent sentence carries a distinct behavioral fact (no triggering, staleness, reference date, partial batches). It is dense and jargon-heavy but not padded with restated name/title.

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 and a fairly complex domain, the description still explains what is returned (state, pending/met items, reasons, actions, evidence) plus edge-case semantics like outdated results and partial batches. Combined with read-only annotations, an agent has enough to call and interpret it 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 seven parameters are already documented, giving a baseline of 3. The description adds domain meaning for the group sub-states (precisa_comprovar, divergente, acompanhar) and the partial-batch counters, but does not clarify the v/id/cnpj/after/limit parameters themselves.

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?

States a specific verb and resource: it reads the participation 'state', pending items and met items with reasons, actions and evidence. It also distinguishes itself from the analyze_participation sibling by emphasizing that it never starts an analysis. The domain jargon (state, batches) keeps it from being maximally crisp, but an agent can tell what it returns.

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?

Gives clear when-not signals: it 'never starts an analysis', 'GET does not run the queue and does not start AI', and a different company/attachments/dossier return outdated results. However it never names analyze_participation as the explicit alternative, so the routing is inferred rather than stated.

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