Buscar Transações

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

With no annotations, the description carries full burden. It reveals default scope and value units but omits pagination, the compact vs. full format behavior (controlled by include_raw), and any side effects or permissions. The description is insufficient for safe autonomous use.

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?

Two sentences with no fluff. Essential information is front-loaded. Every sentence adds 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?

Given 15 parameters, no annotations, and a detailed output schema, the description is far too sparse. It leaves the agent without guidance on how to leverage filters, handle defaults, or interpret results effectively. Completeness is low.

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 only 33%. The description does not explain any parameters or clarify their meaning. It adds no value beyond what the schema already provides or lacks, failing to compensate for the low coverage.

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 it lists transactions with filters. It adds default behavior (current month, cash flow view) and value format (cents). However, it does not explicitly distinguish from sibling tools like despezzas_transaction_overview or despezzas_export_transactions.

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 implicit guidance by noting defaults, but does not specify when to use this tool vs alternatives, nor when not to use it. No exclusions or contextual hints for different scenarios.

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