list_bank_movements

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

With no annotations, the description must fully convey behavioral traits. It only says 'list bank movements', implying a read operation, but fails to mention pagination (limit/offset), order, or what happens on empty results. No details on potential side effects or rate limits.

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 concise with a clear front-loaded purpose and a labeled list of arguments. No unnecessary words, though the Args formatting could be improved for readability. Overall efficient.

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?

The description lacks crucial details for a 7-parameter tool with no output schema or annotations. It does not explain the return format, pagination behavior (limit/offset defaults), or any ordering. The agent may not know how to use pagination or interpret results.

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 adds meaning for 5 of 7 parameters (treasury_id, status, from_date, to_date, search) with examples and types, but omits limit and offset entirely. Since schema coverage is 0%, the description partially compensates but is incomplete.

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 'List bank movements' with optional scoping to a treasury, using a specific verb and resource. It distinguishes the tool from siblings like list_invoices or list_purchases, which deal with different entities.

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 no guidance on when to use this tool versus alternatives such as reconcile_movement or searching via other endpoints. There is no explicit statement of when not to use it or any usage context.

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