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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered; the description adds value by disclosing that multiple tickers can be batched in one comma-separated call and that OHLC history and fundamental data are optional enrichments. Gaps remain around rate limits, API-key requirements, and partial-failure behavior when one ticker in the batch is invalid.

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?

A single front-loaded sentence that names the provider, the resource, the payload fields, and the optional expansions in one pass with no filler. It is dense but readable; the parenthetical example does real work rather than padding.

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?

An output schema exists, so return values need not be spelled out, and the annotations cover the safety profile. However, for a 6-parameter tool with zero schema descriptions, leaving modules and dividends entirely undocumented means an agent cannot confidently construct an enriched query without inspecting the schema by hand.

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% across six parameters, so the description carries the full burden, and it only partially delivers: it explains tickers (comma-separated, with an example) and alludes to range/interval for OHLC history and a fundamental flag. The modules and dividends parameters are never mentioned, and range/interval values are only discoverable from the schema's examples, not from the description.

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 concrete verb and resource — "live quote for one or more Brazilian market tickers" — plus the fields returned (price, change, volume) and the optional OHLC/fundamental expansions, so the agent knows exactly what it gets. It does not distinguish itself from the similarly-scoped sibling quote_list or from brapi_currency/brapi_inflation, so scope boundaries remain unclear.

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?

Usage is only implied: it is the tool for live Brazilian equity quotes, and the example tickers ('PETR4,VALE3') clarify the market context. There is no explicit when-to-use statement, no guidance on choosing it over quote_list or the currency/inflation siblings, and no stated prerequisites such as authentication to brapi.dev.

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