Lấy Báo cáo lưu chuyển tiền tệ

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

With no annotations, description carries full burden. It explains data source, normalization, missing period detection, and that it returns multiple periods. It does not mention side effects, which is appropriate for a read operation.

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?

Description is a single coherent paragraph that front-loads the purpose and then adds details. It could be slightly more structured but is not overly long.

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?

Given no output schema, description covers key output aspects (returned metrics, multiple periods, normalization, missing period detection). It does not detail exact structure but provides sufficient context for an AI agent to understand the tool's function.

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 coverage is 100% with parameter descriptions. The description adds value by explaining that code prefixes differ from other statements, aiding interpretation of results. However, parameter details like pageSize and typeTime are already fully described in schema.

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 retrieves Cash Flow Statement data for a Vietnamese stock from cafef.vn API, lists specific returned metrics (cash flow from operations, cash equivalents), and distinguishes from siblings by noting different code prefixes.

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 cash flow analysis and contrasts with Balance Sheet/Income Statement by mentioning different code prefixes, but does not explicitly state when to use this tool versus alternatives.

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