consultar_conta_receber

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states that the tool consults details, without addressing parameter requirements, return format, or potential side effects. 'Consulta' implies a read-only operation, but the description adds no meaningful behavioral context beyond the action itself.

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, front-loaded sentence that directly states the tool's action and object. It contains no filler, redundancy, or extraneous information, making it highly 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?

For a tool with two optional parameters, no output schema, and no annotations, this description is under-specified. It fails to clarify that at least one identifier code must be provided, what the response contains, or how it differs from related query tools like pesquisar_lancamentos_financeiros.

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 description does not mention either parameter (codigo_lancamento_omie or codigo_lancamento_integracao), leaving their roles entirely to the schema names. With 0% schema description coverage, the agent receives no guidance on which code to supply, whether one is required, or how they relate, making parameter use ambiguous.

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 action ('Consulta detalhes') and the resource ('uma conta a receber específica'). It distinguishes itself from sibling tools like listar_contas_receber (list) and consultar_conta_pagar (different resource), leaving no ambiguity about what the tool does.

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 offers no guidance on when to use this tool versus alternatives. It does not mention listar_contas_receber for multiple records or indicate any prerequisites, exclusions, or conditions for use. The agent must infer usage from the tool name and sibling context.

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