stock_balance_sheet_by_yearly_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the return is a pandas.DataFrame and points at the source endpoint, which is genuinely new information since no output schema exists, but it discloses nothing about period coverage, revision behavior, or authentication.

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?

Efficiently front-loads the purpose on line one, but then appends a raw URL and Sphinx-style ':param/:type/:return/:rtype' boilerplate that restates the same resource name already in the title and first line.

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, read-only data fetch with annotations covering the safety profile and a declared return type, this is adequate but thin. It omits the one thing that would matter most here: how it differs from stock_balance_sheet_by_report_em and the other balance-sheet siblings.

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% and the single param has no schema-level description, so the description must compensate. It partially does: '股票代码；带市场标识' conveys that a market prefix is required, and the sample URL shows 'sh600519' format, but no explicit format spec or example is given for the parameter itself.

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?

States a specific verb/resource pair: Eastmoney stock financial-analysis balance sheet, scoped to annual ('按年度') periods. The '按年度' qualifier implicitly distinguishes it from the by-report sibling, but the description never names that alternative, so the differentiation is only partial.

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, no prerequisites, and no mention of the very close sibling stock_balance_sheet_by_report_em or the by-quarterly variants. The only routing signal is the name's 'yearly' token, which the schema/name already carries, not the description.

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