stock_zh_a_hist_tx

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful return semantics (volume normalized to shares, amount to yuan), which goes beyond the schema, but says nothing about rate limits, auth, or pagination behavior.

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 docstring-style layout is compact and front-loads the source and purpose with a reference URL. Every line maps to a parameter or return, with little filler, though the sphinx :type: lines are somewhat redundant against the 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?

With no output schema, the description usefully declares the return type (pandas.DataFrame) and unit conventions. Combined with the parameter documentation and annotations, an agent has enough to call it, though source differentiation from sibling history tools remains missing.

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 clarifies symbol as a market-qualified code, gives adjust enum values (qfq/hfq/none), and defines timeout, but start_date/end_date are only labeled 'start date'/'end date' with no format, so date syntax (defaults 19000101–20500101) must be guessed from the schema.

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 states a specific verb+resource+source: daily-frequency historical stock data from Tencent Securities. An agent can tell it retrieves daily OHLC history. However, it does not distinguish itself from the many sibling history tools such as stock_zh_a_hist (East Money version) or stock_zh_a_daily, leaving source-selection ambiguous.

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 and no mention of alternatives. The description does not tell the agent when to prefer this Tencent-sourced tool over stock_zh_a_hist, stock_zh_a_daily, or stock_zh_a_hist_min_em, so routing must be inferred entirely from the name suffix.

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