stock_lrb_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 nothing behavioral beyond that — no scope (all stocks vs. one), no data-source quirks, no rate/coverage notes — leaving the behavioral burden entirely on structured fields.

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 and front-loads the dataset identification, with parameter and return info following. The docstring-style :param/:rtype lines and URL are slightly redundant but not wasteful for a 1-parameter tool.

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?

No output schema exists, so the description carries the burden of return-value context; it states the return is a 利润表 DataFrame but never clarifies cross-sectional scope (all listed companies for the given reporting period) or the fields returned. Adequate but leaves a material ambiguity for correct invocation.

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 schema only carries a default, so the description is the sole source of parameter meaning. It usefully specifies the date format (e.g. 20200331, quarter-end YYYYMMDD) and the earliest available period (from 20100331), which is substantive detail the schema lacks.

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 data source and resource (东方财富 income statement data, 利润表), but there is no verb and no differentiation from the many sibling financial-statement tools (e.g. stock_profit_sheet_by_report_em, stock_profit_sheet_by_quarterly_em). An agent cannot tell from the text whether this returns one company's statement or all companies for a period.

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?

The description gives no when-to-use guidance, no prerequisites, and does not mention any alternative. The only usage-adjacent content is the valid date range for the parameter, which is not the same as routing guidance.

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