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

The description provides several behavioral details beyond annotations: it defines the metric computations (e.g., price ÷ same-day nav, effective fee = expense ÷ average net assets), specifies the liquidity threshold, and notes that the use of the share price is same-day. But because there are no annotations and no output schema description, it still lacks information about the or delivery format (e.g., sorted order, number of results, whether it is a table or JSON). The description adds meaningful context, yet the actual runtime behavior remains incompletely disclosed.

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 compact—one sentence with parentheticals—and communicates a large amount of information in a relatively short space. All the clauses are relevant and none are filler. However, the dense parenthetical definitions, while useful, make the wording harder to parse at a glance; a structured bullet list would improve readability without adding length. It is appropriately concise but could be slightly better organized.

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?

The tool is moderately complex with no parameters, no annotations, and no output schema. The description covers the metric definitions and the liquidity scope, which addresses the core data semantics. But it does not specify what the actual result looks like—whether it returns a list of ETF tickers with sorted rankings, how many items are returned, or in what order. Because the output format is omitted, an agent could call the tool correctly but not know how to interpret the response, making the description incomplete for a software agent.

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?

This tool has zero parameters and the schema shows an empty object, so the baseline for parameter semantics is 4. The description clarifies that the tool is a fixed-ranking endpoint and explains that it is 'free', which is helpful but not required. Since there are no parameters, the description doesn't need to explain parameter meaning, and it successfully avoids any parameter-related confusion.

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 clearly identifies the resource (ETFs listed on B3) and the content: it provides a list of most-traded, largest assets, discount/premium, 12-month return, and lowest effective fee. This conveys the tool aims to deliver ETF rankings by multiple criteria, which is clear enough to distinguish it from other data tools. However, it does not explicitly name the ranking behavior or contrast with the sibling 'etf' tool, so it falls shy of full clarity.

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?

There is no explicit 'when to use' or 'when not to use' guidance. The description mentions that only liquid ETFs (> R$1 million/day) are included in certain metrics, which hints at a scope filter, but it does not tell the agent when to prefer this tool over alternatives such as 'etf' or 'fiis_ranking'. With no exclusions or alternative references, the usage context is implied rather than stated.

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