stock_cash_flow_sheet_by_quarterly_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and hazard profile is fully covered by structured data. The description adds only the return type (pandas.DataFrame) and the note that the symbol needs a market identifier, which is useful but modest against an otherwise complete annotation set.

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 purpose is front-loaded in the first line and the docstring lines are brief. The embedded URL is decorative noise that does not aid invocation, but overall it is compact and readable.

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?

There is no output schema, and the description only states that a DataFrame is returned. For a simple single-parameter data fetcher this is nearly adequate, but it omits the reporting-period coverage and whether delisted symbols are supported, which matters given the delisted sibling tool.

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 0%, so the description must carry the parameter burden. It does add real meaning with '股票代码；带市场标识' (stock code with a market identifier), telling the agent the required format beyond the bare string type and default in the schema, which directly compensates for the coverage gap.

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 states a specific verb and resource: fetch the East Money cash flow statement for a stock on a quarterly basis, mirroring the tool name. It clearly identifies what data is returned. However, it never distinguishes itself from close siblings like stock_cash_flow_sheet_by_yearly_em or stock_cash_flow_sheet_by_report_em, leaving the 'by_quarterly' distinction to be inferred from the name alone.

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 when-to-use guidance, no prerequisites, and no mention of the sibling tools that provide the same data on different periodicities. The agent must infer the selection logic entirely from the tool name.

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