stock_zcfz_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, covering the safety profile. The description adds only the return type (pandas.DataFrame) and no context on pagination, coverage, or caveats for this data fetch.

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?

It is compact, but it is an unstructured Sphinx-style docstring with a raw URL and rst tags (:param, :type, :return) rather than front-loaded prose. Nothing is wasted, but the format is not optimized for an agent reading it as an instruction.

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 single-parameter, no-output-schema data fetch, the description supplies the parameter semantics and the return type, which is nearly sufficient. It is incomplete in that it does not differentiate this tool from the many sibling balance-sheet and 业绩快报 endpoints, leaving selection ambiguous.

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 carries the burden and does so well: it gives the accepted date values (20200331 format), the type (str), and the lower bound (从 20100331 开始). The default value in the schema is not explained, but the format and range are the critical semantics.

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 the source (东方财富数据中心 业绩快报) and the dataset (资产负债表), so an agent can infer it returns balance-sheet rows. However it never states a verb or scope in a way that distinguishes it from close siblings such as stock_balance_sheet_by_report_em or stock_zcfz_bj_em; the name plus title essentially label a dataset rather than describe an action.

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 guidance on when to use this tool versus alternatives. The 业绩快报 vs 报表 distinction that separates it from stock_balance_sheet_by_report_em is never stated, and no prerequisites or exclusions are given.

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