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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, but the description still adds substantial context beyond them: anonymous access is open for any ticker one at a time, rate limits of 1000/hour and 10000/day per address (key-based limits with `chave_api`), and that historical `as_of` views require a key and are absent here. It also notes the `citacao` field is returned.

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?

Dense but every sentence carries information: purpose, granularity switch, domain exclusion, access model, limits. Front-loading is good, though the access/limit paragraph is a bit crammed and could be split more cleanly for scanning.

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?

No output schema exists, so the description carries return-value burden; it names the key fields and the `citacao` field but doesn't describe the response shape (e.g., period-by-period rows or nesting). For a read-only, well-annotated tool this is close to complete, with only return structure a minor gap.

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 coverage is 0% and there are three params, yet the description explains all three: `trimestral` granularity semantics, `chave_api` effect on rate limits, and that `ticker` accepts any single stock ticker. Only the ticker string format and how to obtain a key are left implicit, keeping it just under a 5.

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 — standardized CVM-sourced financial accounts (receita, EBIT, lucro, PL, dívida, caixa) for a stock — with the auditorable origin of each line. It also explicitly separates itself from the sibling `fii`, which covers FIIs, so an agent can pick correctly without opening either schema.

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?

Explicitly states the domain restriction ('Só ações'), explains why FII data isn't here and routes to `fii` as the alternative, and clarifies the `trimestral` choice (DFP annual vs ITR Q1-Q3). It also flags what is NOT available (past `as_of` balances, old versions) and the auth/rate-limit tradeoff.

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