listar_indexadores

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Lista' conveys a read-only listing operation and the setup context adds useful behavioral framing. However, it does not disclose the effect of the optional 'atualizar' parameter, such as whether it forces a refresh or changes output.

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 two short, efficient sentences. The main purpose is front-loaded, and the setup directive earns its place. There is no filler or redundant restating of the tool name.

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?

This is a simple list operation with one optional boolean parameter and no output schema. The description is adequate for basic invocation and context, but the undocumented 'atualizar' parameter is a real gap, and there is no mention of what the returned data looks like. Additional detail would make it complete.

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%, and the description never mentions the 'atualizar' parameter. The agent is left to guess whether it means update the cache, re-fetch from Sienge, or something else. The description adds no meaning beyond the raw schema field.

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 that the tool lists Sienge indexadores, adding relevant context that a title needs one and that 'Real' is the typical value. It is specific enough to identify the resource, though it does not explicitly distinguish itself from the sibling listar_* tools.

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 explicit usage context: use it during setup to define SIENGE_INDEXADOR_PADRAO. It does not mention when not to use it or alternatives, so it falls short of the highest level, but the guidance is clear and actionable.

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