get-fiis

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

No annotations are provided, so the description alone must convey behavioral traits. It only states the tool searches for indicators, but does not disclose whether it is read-only, what data is returned, or any side effects. It lacks information on authentication, rate limits, or other behaviors beyond the basic purpose.

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 sentence with no unnecessary words. It is front-loaded with the core action and resource. It is appropriately concise for a tool with one parameter.

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 has no output schema, and the description does not explain what is returned (e.g., which indicators, format). Given the presence of many sibling tools, the description should provide more context about the output to avoid ambiguity. The current content is insufficient for an agent to use this tool effectively.

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 coverage is 100% as the sole parameter 'tickers' has a description with an example. The tool description does not add extra meaning beyond the schema; it merely restates the purpose. Per guidelines, with high schema coverage the baseline is 3, and the description does not improve it.

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 tool's purpose: 'Buscar indicadores fundamentalistas de FIIs (Fundos Imobiliários)' meaning 'Search for fundamental indicators of FIIs (Real Estate Funds)'. It specifies the action (search) and the resource (FIIs), and implicitly distinguishes from sibling tools like 'get-acoes' (stocks) and 'get-fiagros' (other fund types) by focusing on real estate fund indicators.

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 provides no guidance on when to use this tool versus its siblings, such as 'get-fundos-imobiliarios' or 'get-fii-infra'. There is no mention of prerequisites, alternative tools, or conditions for use. The agent receives no context to choose this tool over others.

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