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

No annotations are provided, so the description carries the burden. It adds useful behavioral context by stating the data comes directly from official company reports and covers operating, investing, and financing flows. However, it does not disclose return format, pagination, line-item variability, or other limitations such as period-specific nuances.

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 two sentences with no redundant content. It front-loads the core purpose and adds a concise explanation of the data's content and source. Every word contributes to understanding.

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 no output schema and no annotations, the description covers the conceptual purpose and data origin but omits response structure, result format, and explicit usage boundaries. The parameter schema is fully covered, yet the lack of return-value details leaves the description only minimally viable for an agent.

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 input schema already describes all three parameters (symbol, period, limit) with clear descriptions and an enum for period, providing 100% coverage. The description adds no additional parameter-level semantics beyond those in 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 views cash flow statements 'as reported' by the company from official reports, using the specific verb 'View' and identifying the resource. This distinguishes it from siblings like getCashFlowStatement or getCashFlowStatementTTM that likely provide normalized or calculated data.

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 analyzing official, as-reported cash flow data, but it does not explicitly state when to prefer this tool over alternatives or mention exclusions. There is no reference to sibling tools such as getCashFlowStatement, getCashFlowStatementGrowth, or bulk variants, so guidance is only inferred.

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