list_money_movements

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

The description claims to list 'all' money movements, but annotations include openWorldHint=true, indicating the response may not be exhaustive. This contradiction undermines transparency. Additionally, no details about pagination, ordering, or response format are provided.

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 sentence that efficiently conveys the tool's purpose and clarifies what money movements are. No filler or unnecessary text.

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?

Despite low complexity, the description omits critical information: the contradiction with openWorldHint, the return format (list of objects), and any limitation on what 'all' means. The output schema is missing, so more context was needed.

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 describes the one parameter (budgetId) with default behavior. The description adds no extra meaning beyond the schema, so 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?

The description clearly states the tool lists all money movements, defined as budget re-allocations between categories. It distinguishes from sibling tools like get_money_movements_by_month and list_money_movement_groups by specifying the scope.

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 usage for listing all money movements but provides no guidance on when to use this tool over alternatives like get_money_movements_by_month. The openWorldHint suggests the list may be incomplete, but no exclusion criteria are given.

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