stock_lh_yyb_capital

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the source URL and return type (pandas.DataFrame), which is useful context, but it does not disclose other behavioral traits such as pagination, date range coverage, or network dependency. No contradiction with annotations.

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 concise at three lines: a title, a source URL, and a return type. It is front-loaded and readable, though '资金实力最强' is repeated in the title and return line, adding slight redundancy.

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?

The tool is simple with no parameters, but the description does not explain what columns or ranking criteria the returned DataFrame contains, nor how it differs from other longhu ranking tools. Given the absence of an output schema, additional structural detail would improve completeness.

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 tool has zero parameters and schema coverage is 100% (empty properties object). The baseline of 4 applies because there are no parameter semantics to clarify, and the description correctly implies a no-arg call.

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 tool as providing Tonghuashun's business department ranking by strongest capital strength ('资金实力最强'). It names a specific resource (营业部排名) and includes the source URL, distinguishing it from sibling tools like stock_lh_yyb_control and stock_lh_yyb_most, though it lacks an explicit verb like 'fetch'.

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. With many similar longhu-related sibling tools (e.g., stock_lh_yyb_control, stock_lh_yyb_most), the description does not specify use cases, exclusions, or alternatives, leaving the agent to rely on the title alone.

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