stock_cash_flow_sheet_by_report_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only a source URL and ':rtype: pandas.DataFrame', which conveys little about what the returned DataFrame contains (units, number of periods, column semantics). The first line merely restates the annotation title.

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 body is short, but the opening line duplicates the annotation title and the URL is raw context rather than actionable guidance. The param/return Sphinx-style lines are compact and front-loaded, so it is efficient without being especially well-structured.

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?

For a one-parameter read-only tool whose annotations cover safety and whose return type is stated, this is roughly adequate. The meaningful omissions are the semantics of '按报告期' versus the quarterly/yearly variants and any hint about the units or breadth of the returned financial data.

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 compensate, and it partially does: ':param symbol: 股票代码；带市场标识' tells the agent the symbol needs a market prefix (e.g., the SH600519 default visible in the schema/URL). It stops short of specifying the exact format, accepted market prefixes, or an example within the param line, leaving real gaps.

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 names a specific resource and scope: East Money (东方财富) stock cash flow statement (现金流量表) for a financial analysis, organized by report period (按报告期). This is more than a restatement of the name. However, it never explains how 'by report period' differs from the sibling tools stock_cash_flow_sheet_by_quarterly_em and stock_cash_flow_sheet_by_yearly_em, so an agent must infer the distinction.

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 quarterly/yearly cash flow siblings that are the natural alternatives. The agent is left to infer selection 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.