get_shareholder_info

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

No annotations are present, so the description must fully disclose behavioral traits. It only states the purpose—read operation for shareholder data—without mentioning safety (e.g., read-only nature), rate limits, or data scoping. This is insufficient for an AI agent to understand impact.

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 sentence, making it very concise. However, it is minimal and lacks any structural elements like front-loading key information. It earns points for brevity but loses some for not being more informative.

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?

Given the tool has only two parameters, an output schema exists (so return values are documented), and no annotations, the description is adequate but not complete. It lacks context on when to use this tool and what the output represents, which could lead to incorrect invocations.

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 input schema covers 100% of parameters with descriptions and enums. The description adds no extra meaning beyond the schema, so it meets the baseline for high coverage. However, it does not clarify the expected format for 'symbol' beyond what the schema provides.

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 indicates the tool retrieves shareholder information for a specified stock. It distinguishes from sibling tools like get_stock_basic_info and get_financial_metrics, though it could be more explicit about the exact data included.

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 usage guidelines are provided. The description does not mention when to use this tool versus alternatives, nor does it offer context on prerequisites or typical use cases. Given many sibling tools, this omission hinders correct tool selection.

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