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

With no annotations, the description carries the full burden and does substantial work: it discloses the first-page-only cap (up to 5 rows), the absence of pagination input, the per-call cost (0.011000 USDC), and explicit disclaimers about identity/completeness attestation and safety guarantees. It does not cover authentication or error behavior, keeping it out of the top tier.

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 purpose and key constraint are front-loaded, but the text is bloated by restated disclaimers – 'The list does not independently attest entity identity or completeness' and 'No completeness or safety guarantee' convey overlapping caveats, and the pricing sentence interrupts the flow.

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?

With no output schema and a nested, undocumented argument object, the description supplies the essential operational context an agent needs: data dependency, page-size ceiling, no pagination, and cost. It stops short of fully specifying the argument payload, which is delegated to another 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 0% and the lone 'arguments' object is opaque (additionalProperties: true, no property descriptions). The description partially compensates by naming the required company_id from cn_data_v3_company_detail, but it defers the actual argument structure to get_cn_data_tool_schema('v3_shareholder_list') rather than documenting it inline, so gaps remain.

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 opening sentence names a specific resource ('Recorded shareholders') and ties it to the company_id sourced from cn_data_v3_company_detail, so the agent knows this returns a shareholder roster. It is distinguishable from sibling list tools by resource, though it never explicitly contrasts with near neighbors like key_person_list.

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?

It states a prerequisite (Jinghai company_id from cn_data_v3_company_detail) and notes that additional pages require separate requests, which is useful context for when this tool applies. However, it gives no explicit when-not guidance or comparison against alternative tools that return related entity lists.

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