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

No annotations are provided, so the description carries the full behavioral burden. It mentions data sources (Genesis Bolsa, CVM + B3) but says nothing about permissions, rate limits, freshness, failure modes for non-public companies, or what the tool returns beyond a loose field list.

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 description is a single compact sentence and the key condition is front-loaded. It is concise, but the terseness leaves out essential invocation guidance, making it under-specified rather than optimally structured.

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 annotations, no output schema, and an undocumented parameter, the description is too thin for an agent to call the tool confidently. It names some return fields but omits parameter semantics, error behavior, and relationship to sibling tools, leaving significant gaps.

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?

The single required parameter, cnpj, is not described at all; schema description coverage is 0%. The description does not explain expected CNPJ format, validation, or whether formatting characters are accepted, so it fails to compensate for the schema gap.

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 indicates the tool returns B3 stock data (tickers, quote, market value, P/L, P/VP) for open companies, which gives a recognizable resource. However, it lacks a clear action verb and does not explicitly distinguish this lookup from sibling tools like consultar_cnpj or buscar_empresa. Purpose is inferable but not sharply defined.

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?

The only usage condition is 'if the company is a publicly traded company on B3', with no guidance on when to choose this tool over alternatives such as consultar_cnpj, buscar_empresa, or listar_concorrentes. There are no exclusions or downstream selection cues.

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