stock_hold_management_person_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well-covered. The description adds the data source URL and the pandas.DataFrame return type, but says nothing about failure modes, data freshness, pagination, or other runtime behavior.

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 compact, with about five lines covering source, URL, parameters, and return type, with no filler. The structure is slightly marred by the misaligned :param/:type docstring entries and the raw encoded URL, but it remains front-loaded and efficient.

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?

Since no output schema exists, the description should compensate by detailing return values; it only names the return ('人员增减持股变动明细') and type (pandas.DataFrame) without listing expected columns. It also does not clarify how name and symbol combine, though both have defaults, leaving agents uncertain about result fields.

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?

With 0% schema coverage, the description compensates by providing Chinese semantics: symbol=股票代码 (stock code) and name=高管名称 (executive name), adding meaning beyond the bare string schema. However, the :type docstring lines are swapped with the :param lines, and no format constraints are given beyond the defaults.

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 resource: East Money executive-holdings personnel increase/decrease shareholding change details, reinforced by the source URL. However, it lacks an explicit action verb and does not distinguish itself from the closely named sibling stock_hold_management_detail_em.

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?

Usage is implied through the parameter docs (query by stock code and executive name) and the breadcrumb path under 数据中心-特色数据-高管持股. No explicit when-to-use, when-not-to-use, or alternative tool guidance is provided, especially versus sibling tools like stock_hold_management_detail_em.

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