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

With no annotations present, the description carries the disclosure burden. It reveals the data sources (CVM + B3), the scoped information returned, and the API-key requirement for non-BOVA11 tickers. It does not mention rate limits or explicitly state read-only behavior, but the query-like nature plus detailed output sections give adequate transparency for an agent.

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 dense but well organized: the first sentence front-loads the core purpose and output contents, and the second delivers the access caveat. Every clause adds information, though the long comma-separated list makes it slightly heavier than necessary.

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?

There is no output schema, so the description must explain what the tool returns, and it does so thoroughly: portfolio overlap, premium/discount, monthly rates, returns by quote and price, and registration data. Combined with the API-key guidance, an agent has enough context to invoke the tool for the intended use case.

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 schema only supplies titles and defaults, and schema coverage is 0%, so the description must compensate. It does: 'BOVA11' provides a concrete ticker example, and the sentence about requiring chave_api for all other ETFs clarifies the otherwise misleading empty-string default on the chave_api parameter.

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 states a clear, specific purpose: 'Detalhe de um ETF' and enumerates the exact data blocks returned, such as cadastro CVM+B3, informe diário, ágio/deságio, taxa efetiva, carteira, sobreposição, and retornos. This scope distinguishes it from broader siblings like etfs_ranking, which clearly focuses on ranked lists rather than a single ETF's detailed profile.

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 description gives clear contextual guidance: BOVA11 is freely available for testing, while all other ETFs require a chave_api (free or Pro). It does not explicitly compare this tool with alternatives or state when not to use it, so it stops short of a 5, but the access and prerequisite guidance is concrete and actionable.

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