Listar Metodos

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

No annotations, so the description carries the burden. It discloses the two-step discovery workflow (search by intent, then call descrever_metodo) and implies a read-oriented listing scope, though it doesn't spell out pagination or that some listed methods may write (only hinted via the apenas_leitura param). Adds real behavioral context beyond structured fields.

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?

Front-loads the key framing ('Passo 1 para...') and stays compact across three short blocks. Slightly noisy with all-caps emphasis and parentheticals, but each sentence carries routing or workflow value.

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 needn't be explained, and the discovery/sequencing role is well articulated. Minor gap: it never clarifies whether listed methods include write operations, which matters for an agent deciding between this and listar_telas.

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 100%, so the schema already documents busca, limite, and apenas_leitura. The description reinforces the intent-search pattern ('Busque pela intenção dela') but adds no syntax or format detail beyond what the schema provides; baseline 3 applies.

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 specific verb+resource ('listar_metodos') and frames it as 'Passo 1 para RELATÓRIOS e CONSULTAS financeiras' (web service), which clearly distinguishes it from the operating counterpart listar_telas. An agent can tell this is the discovery layer for data-oriented methods without opening any schema.

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?

Explicitly states when to use it ('quando a pessoa quer DADOS: inadimplência, contas a pagar, fluxo de caixa...'), gives concrete intent keywords, names the alternative for operating (listar_telas), and prescribes the next step (descrever_metodo). Full when/when-not/alternative routing.

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