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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds valuable context beyond that: it specifies the output is JSON, lists what is included (formula, CVM accounts, profit basis), and gives a critical semantic warning about how margem_liquida and roe use different profit bases. It also notes the tool is free.

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 front-loaded with what the tool provides and is reasonably concise. The final 'Gratuito' adds a minor but useful fact, and the middle warning is justified by its importance for correct comparisons. No major filler, though the structure could be slightly tighter.

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?

For a zero-parameter reference tool with no output schema, the description gives a good indication of the return content (JSON, formula, CVM accounts, profit basis) and a key semantic caveat. It stops short of detailing the full return shape, but it is likely sufficient for an agent to understand what calling it yields.

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 tool takes zero parameters, so there is no parameter semantics to explain. Per the baseline for zero-parameter tools, a 4 is appropriate; the description correctly focuses on content rather than nonexistent inputs.

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 states the resource: methodology of indicators, including formula, CVM accounts, and the profit basis for each. It distinguishes itself from most siblings by describing specific content, but it does not explicitly differentiate from the close sibling 'metodologia', leaving some ambiguity about which one to call.

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 an interpretation caveat ('IMPORTANTE para comparar corretamente...'), but it never states when to use this tool versus alternatives such as 'metodologia' or 'indicadores_anuais'. No exclusions or conditional guidance are provided.

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