get_stock_circulate_stock_holder

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

No annotations exist, so the description must disclose behavioral traits. It does not state that the tool is read-only, rate limits, or any side effects. The term '流通股东' suggests a query, but safety is not explicitly communicated.

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 a single short sentence in Chinese, very concise and front-loaded. It could benefit from a slight expansion (e.g., output summary) but is not overly verbose.

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?

Despite having an output schema (not shown here), the description does not hint at the return structure. For a stock data tool, agents would benefit from knowing what fields are returned. Additionally, no annotations compensate for missing behavioral context.

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%, with both parameters described adequately in the schema. The description adds no extra meaning beyond what the schema provides (e.g., symbol format, output_format options). Baseline score of 3 is appropriate.

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 states the tool retrieves circulating shareholder data for a specified stock (流通股东情况). The verb '获取' (get) and resource '流通股东情况' make the purpose specific. However, it does not explicitly differentiate from siblings like 'get_shareholder_info' or 'get_stock_basic_info'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., when to use this vs get_shareholder_info). There is no mention of prerequisites or context for invocation.

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