wafeq_reports_cash_flow_list

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral details beyond the schema: it emphasizes that date_after/date_before are both required, that there is no date_from/date_to, and that a whole-period rule is validated before sending.

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 text is compact and front-loads the read-only tag and endpoint, but the standalone 'Cash Flow' heading duplicates the title and the emoji decoration adds little. The remaining sentences are purposeful.

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 read-only report tool, the description plus fully documented schema covers required parameters, date-range rules, optional grouping, and filters. It is slightly incomplete in not spelling out the whole-period rule itself or what the returned report contains, but it is otherwise sufficient.

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?

With 100% schema description coverage, the baseline is 3, but the description adds extra meaning by calling out required range bounds and explicitly ruling out date_from/date_to. It also confirms how currency and group_by shape the report, which helps an agent select values correctly.

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?

Description uses a specific verb ('Generate') and resource ('cash flow report'), and names the exact endpoint GET /reports/cash-flow/. It is clearly distinct from sibling report tools like wafeq_reports_balance_sheet_list and wafeq_reports_profit_and_loss_list.

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 gives no explicit guidance about when to choose cash flow over the other report list tools. It only references the profit-and-loss rule for date handling, not a comparison of use cases or exclusions.

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