stock_zcfz_bj_em

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds return type (pandas.DataFrame) and date-range context, but does not add auth, rate-limit, or other behavioral traits beyond the annotations.

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 short and mostly front-loads the source and dataset. The URL and :param/:return lines are structured and not excessive, though the URL is arguably non-essential.

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 data-retrieval tool with no output schema, the description gives source, date format, and return type. However, in a very large sibling set it fails to clarify scope ('bj') or when to choose it over closely named alternatives, leaving meaningful selection ambiguity.

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 parameter meaning. It supplies the date format/enum examples (quarter-end strings from 20100331) and return type, substantially compensating for the missing schema description, though the default value 20240331 is not explained.

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 identifies the dataset (东方财富 balance sheet from annual/quarterly/earnings reports), so the high-level resource is clear. However, it does not explain the 'bj' scope or distinguish this tool from closely named siblings such as stock_zcfz_em or stock_balance_sheet_by_report_em, leaving purpose only partially resolved.

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?

No when-to-use guidance, prerequisites, or alternatives are provided. The only usage-like detail is the date parameter's allowed values, which is parameter semantics rather than selection guidance.

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