Cashflow Get Cashflow Trends

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. However, the description adds no behavioral context beyond the word 'Get'—it does not explain the nature of the returned trends, how filters affect results, or what the interval grouping means.

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 and free of filler. However, it is under-specified to the point of providing little value, so it is not 'appropriately sized' for the tool's complexity.

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?

With six parameters, two required, filter objects, enums, and no output schema, this tool needs a substantive description. 'Get cashflow trends' is completely inadequate: an agent cannot tell what the trends represent, how the date range is aggregated, or how filters and output modes affect 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?

Schema description coverage is only 33%, with only fields and output_mode having descriptions. The description does not compensate: it explains none of the six parameters, leaving start_date, end_date, interval, and filters semantically underdocumented for an agent.

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 'Get cashflow trends' is essentially a restatement of the tool name and title, so it falls into tautology territory. It gives no concrete detail about what a cashflow trend is or how this tool differs from sibling tools like cashflow_get_cashflow_summary and cashflow_get_cashflow_breakdown.

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?

There is no guidance about when to use this tool versus the closely related cashflow summary and breakdown tools. The interval parameter implies time-series aggregation, but the description itself says nothing about appropriate use cases or alternatives.

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