gangtise_cash_flow

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description merely states it queries data, without mentioning any side effects, permissions, rate limits, or data characteristics. For a data retrieval tool, this is insufficient transparency.

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 a single sentence plus a date context note, which is concise and front-loaded. However, the date note is a meta-instruction that could be considered extraneous. Overall, it is efficiently structured without redundancy.

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?

The tool has 7 parameters and no output schema. The description provides a high-level summary but lacks details on the return format, pagination, or the meaning of 'cumulative' (year-to-date). For a complex financial data tool, this is incomplete guidance for an AI 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?

Schema description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond what the schema already provides for each parameter. The description lists the supported filter types but does not elaborate on their values or usage beyond the 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 explicitly states '查询A股现金流量表（累计口径）' (query A-share cash flow statement, cumulative basis), which is a specific verb and resource. The scope 'A股' distinguishes it from sibling tools like gangtise_cash_flow_hk (Hong Kong) and gangtise_cash_flow_quarterly (quarterly), making the purpose clear and distinct.

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 only mentions supported filters (period, fiscal year, report type) but does not explain when to use this tool versus alternatives like gangtise_cash_flow_quarterly or gangtise_cash_flow_hk. No explicit guidance on when not to use or which context to prefer. The naming provides implicit hints, but not enough.

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