问财选港股（同花顺问财）

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It usefully discloses the data source (同花顺问财) and the natural-language query style, implying a read-only screening operation. However, it does not describe output format, pagination behavior, or error/rate-limit characteristics.

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 two sentences with no redundancy. It front-loads the core purpose and follows with the data source and supported filter categories, making it efficient and easy to scan.

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 low-complexity screening tool with three documented parameters and no output schema, the description covers the essential purpose, query categories, and data source. It omits explicit sibling routing and output details, but these are not critical given the simple, read-only nature of the 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 coverage is 100%, so the parameters themselves are documented. The description adds meaningful semantic context by enumerating supported query dimensions and multi-condition combination, helping the agent craft an appropriate natural-language query value beyond what the schema states.

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 action and resource: screening Hong Kong stocks via natural language queries. It lists concrete filter dimensions (行情指标、财务指标、行业概念、陆港通), making it clearly distinguishable from siblings like select_astock and select_usstock by asset class and query style.

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 clear context for when to use the tool: when a user wants Hong Kong stock screening with natural language and multi-condition filters. It does not explicitly name sibling alternatives or state when not to use it, so it stops short of a 5.

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