stock_profit_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 the data source (East Money) and confirms the return type is a pandas DataFrame, but says nothing about network/rate-limit behavior or the shape/content of the returned statement.

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?

Compact docstring layout with the identifier/resource line front-loaded, then param semantics, then return (利润表-报告期) and rtype (pandas.DataFrame). The return line largely repeats the opening line, and the embedded URL is only marginally useful, but there is no bloat.

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 lookup with no output schema, the description covers the required input semantics and the return container type. It does not describe the columns/fields returned, which columns correspond to which reporting periods, or how many periods come back – gaps that matter for a financial statement tool.

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% – the symbol property has only a default (SH600519) and no description. The description compensates by explaining that symbol is a stock code that must carry a market prefix (带市场标识), which is exactly the non-obvious detail an agent needs, though it gives no format examples or market-prefix enumeration.

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 the source (东方财富), the resource (利润表/income statement), and the scoping dimension (报告期/report period), so an agent knows this returns East Money income-statement data keyed by reporting period. It does not, however, distinguish itself from siblings such as stock_profit_sheet_by_quarterly_em, stock_profit_sheet_by_yearly_em, or stock_profit_sheet_by_report_delisted_em, leaving the agent to infer the granularity difference.

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 is provided. The description never mentions the quarterly/yearly/delisted variants of the same data, nor when the report-period view is preferable, so the agent gets no routing information among near-identical siblings.

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