listar_contas_pagar

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'lists accounts payable with filters.' It does not mention pagination behavior, default ordering, how filters interact, any access requirements, or the return format, and it references a filter parameter that isn't in 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 a single concise sentence that is front-loaded and easy to parse. It earns its place by stating the core action and available filter categories, though it sacrifices detail for brevity.

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 9 optional parameters, no annotations, and no output schema, this description is too thin. It omits essential context about pagination, sorting, filter value formats, and what the returned data looks like, making it insufficient for an agent to fully understand the tool's behavior.

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 schema has 9 parameters with 0% description coverage, and the tool description provides no parameter details. Worse, it mentions a 'fornecedor' filter that does not correspond to any schema property (the closest is 'filtrar_cliente'), so it actively misleads rather than clarifying parameter semantics.

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 lists accounts payable (contas a pagar) with filters, distinguishing it from sibling tools like listar_contas_receber. However, it mentions a 'fornecedor' (supplier) filter that does not exist in the input schema, which introduces a minor inaccuracy.

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 implies this tool is for listing accounts payable when filtering by status, date, or supplier is needed, but it gives no explicit guidance on when to choose this over alternatives like consultar_conta_pagar or listar_contas_receber. There are no exclusions or alternative tool mentions.

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