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

No annotations are provided, so the description carries the disclosure burden. It clearly conveys this is a read/data-lookup operation by enumerating returned data groups, and the presence of an output schema covers structural expectations. It doesn't explicitly state side-effect-freeness, but nothing in the description implies mutation; content disclosure is solid.

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 and well ordered: content first, usage trigger second, exclusion warning last with a clear ⚠️ marker. No filler sentences. The opening sentence is dense with comma-separated items, but each earns its place given the data variety.

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?

Complete for a single-stock query tool: content, usage trigger, and the alternative tool are all covered, and the output schema handles return structure. Minor gaps (pagination, data-availability caveats) are non-critical for a one-parameter stock lookup.

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 100% for the single parameter `code`, so the schema already documents it. The description reinforces the stock-level scope but adds no new format or syntax detail beyond 'sh600667'. Baseline 3 is appropriate when the schema carries the documentation weight.

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 clear resource (single-stock trading data) with enumerated content groups (主力资金/龙虎榜/大宗交易/融资融券) and explicitly scopes it to one stock. It names the sibling it is not (ashare_lhb for market-wide lists), so an agent can disambiguate without opening either schema.

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?

Gives an explicit trigger ('用户问某只股票的主力资金/机构动向用这个') and an explicit exclusion with a named alternative ('全市场榜单请用 ashare_lhb——本工具只针对单只股票'). When-to-use and when-not-to-use are both stated directly.

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