get_cash_flow

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

Discloses it is a premium-gated read operation and requires IWMM_API_KEY. No discussion of side effects, rate limits, or return structure. Lacks detail for an unannotated tool.

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 short sentences, front-loaded with purpose, then constraints. Every word earns its place.

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?

Covers purpose and auth, but with no output schema or annotations, the description leaves gaps (e.g., time period, return format). Adequate for a simple tool but not fully complete.

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?

No parameters exist; schema coverage is 100% trivially. Description adds no parameter info, but baseline for zero-param tools is 4.

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?

Clearly states tool retrieves cash flow (money in vs out from BUY/SELL transactions). Differentiates from siblings like get_cost_basis or get_realized_gains by focusing on net cash movement from trades.

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?

Mentions premium gating and API key requirement, giving prerequisites. No explicit guidance on when to use vs alternatives; context is implied but not compared to sibling financial tools.

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