listar_contas_dre

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

With no annotations, the description fully discloses key behaviors: it is not paginated, returns the entire structure in 'dreLista', lists all returned fields with meanings, and explains level semantics. It also notes the read-only limitation, providing comprehensive behavioral context beyond the schema.

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 four sentences, each adding necessary information: purpose, response shape, level semantics and filter usage, and read-only note. It is front-loaded with the main purpose and avoids fluff, making it both concise and well-structured.

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?

Given no annotations or output schema, the description covers the essential aspects: it explains what is returned, the meaning of levels, the availability of a filter for other operations, and the read-only constraint. This is sufficient for an agent to select and invoke the tool correctly without additional context.

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 0%, and the description only explains 'apenas_vinculaveis' (for getting valid codes for other tools), while leaving 'apenas_ativas' unexplained. The schema provides only titles and defaults, so the description adds some value but does not fully compensate for the missing parameter documentation.

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 opens with a specific verb and resource: 'Lista a estrutura de contas do DRE', clearly identifying the tool's function. It further distinguishes itself by specifying the non-paginated nature and the detailed fields returned, setting it apart from sibling listing tools like listar_categorias.

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 explicit usage guidance: 'Use apenas_vinculaveis=True para obter direto os códigos válidos em incluir_categoria/alterar_categoria', directly telling when to use the filter. It also states the API is read-only for DRE, implying it should not be used for modifications, which is a clear when-not.

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