stock_profit_sheet_by_quarterly_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and reproducibility profile is covered without description help. The description adds the upstream source (an emweb URL) and the return type (pandas.DataFrame), which is modest but genuine value beyond the annotations; it says nothing about rate limits, pagination, or data latency.

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 content is compact and front-loaded with the data-set identifier, followed by a source link and standard Sphinx param/return lines. Nothing is padded, though the bare URL is of limited utility to an agent and the docstring boilerplate (:type, :rtype) is redundant next to the structured schema.

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 fetch, the safety profile (annotations), parameter format hint, and return type together cover most of what is needed to call it. The notable gap is the absence of any statement distinguishing this quarterly variant from the report/years/delisted siblings in the same family, which is the main ambiguity an agent faces here; no output schema exists so the description needn't detail columns.

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 schema documents only a string named symbol with default SH600519 and no explanation. The description partially compensates by stating 股票代码；带市场标识, i.e. that the code must carry a market prefix, which is meaningful format guidance an agent could not get from the schema alone; it stops short of giving a format example or listing valid market prefixes.

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 a specific resource and source: 东方财富 (Eastmoney) income statement (利润表) by single quarter (按单季度), which tells an agent exactly what data set is returned. However, it offers no differentiation from close siblings such as stock_profit_sheet_by_report_em or stock_profit_sheet_by_yearly_em, whose names differ only in the period basis, leaving the agent to infer the distinction from names alone.

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 when-to-use guidance, no statement of when this tool should be preferred over the by_report or by_yearly income-statement siblings, and no mention of prerequisites or exclusions. The description only names the data set, so selection must be inferred entirely from the tool name.

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