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

Annotations already declare the safety profile (readOnly, idempotent, closed-world, non-destructive), so the lower bar applies, and the description still adds real substance: the source attribution (declared by B3 vs found by us), the price-agreement states, and the same-day grouping rule. It does not cover pagination or errors, so it falls short of a 5.

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?

Three front-loaded sentences: resource/types first, then the same-day multiplier semantics, then the auth detail. Dense and jargon-heavy but every clause carries information; the all-caps emphasis is stylistic noise rather than wasted length.

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 steps in usefully by naming the efeito_liquido_do_dia multiplier and the confirmation states, giving the agent a sense of the return. Annotations cover the safety profile, so the remaining gap (no explicit output shape or error behavior) is minor for a read tool.

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%, so the description carries the full parameter burden. It partially compensates by explaining that chave_api is required for all tickers except WEGE3, but neither ticker format nor what chave_api is remains unexplained. Partial compensation supports a 3.

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 resource with enumerated event types — desdobramentos, grupamentos, bonificações, cisões of a company — plus the distinguishing dimensions (source, price confirmation). This is cleanly separable from the nearest sibling, dividendos, which covers a different class of event.

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 an access prerequisite (WEGE3 free; other tickers require chave_api), which is useful for invocation, but never says when to prefer this tool over siblings or what situations call for it versus dividendos/scores. Usage is only implied by the resource itself.

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