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

With no annotations provided, the description carries the full burden of behavioral disclosure DNA. It names the data categories but does not state whether the operation is read-only, what the returned data covers, or any limitations or freshness considerations. This is a meaningful gap for an unannotated tool.

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 description is one compact sentence that front-loads the core data categories and immediately follows with concrete user query triggers. There is no filler or redundancy.

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?

The description covers the primary use case and the tool has an output schema, so return-value documentation is not strictly necessary. However, the parameter semantics are underspecified for a single required code parameter, and the overlap with ashare_lhb is not resolved, leaving some ambiguity for the agent.

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?

The schema provides only a 'code' parameter with 0% description coverage, and the description does not explain the expected format, meaning, or possible values of 'code'. An agent can infer it likely refers to an A-share stock code from the tool context, but the description adds no explicit parameter guidance.

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 clearly identifies the tool as a comprehensive financial data tool covering funds flow, Dragon-Tiger List, block trades, and margin trading, and maps it to specific user query topics. However, it does not explicitly distinguish itself from the dedicated sibling ashare_lhb, so the differentiation is somewhat implicit.

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 explicit user-query signals ('主力资金/龙虎榜/机构动向/融资融券') for when to select this tool. It does not provide exclusions or mention when a sibling like ashare_lhb should be used instead, which would make the guidance fully complete.

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