stock_lhb_jgmx_sina

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is known. The description adds only the return type (pandas.DataFrame) and a URL, but no behavioral context such as what data is included, whether it is real-time/historical, or any rate limits. This adds minimal value beyond 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 very short, but it is repetitive: the Chinese title appears twice ('龙虎榜-机构席位成交明细' in the title and in the :return: line). The URL is additional but not descriptive. It is front-loaded but under-specified, making it concise yet redundant.

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?

There is no output schema, so the description should describe the returned data content. It only provides a return type and a repeated title, not what columns or data it contains. The description is insufficient for an agent to understand what data will be returned or how to interpret it, given the tool's clear niche.

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, so parameter semantics are not applicable. The baseline of 4 is appropriate because there are no parameters for the description to explain, and the schema is empty (100% coverage). The description correctly does not need to elaborate on parameters.

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 identifies the specific resource as '龙虎榜-机构席位成交明细' (Dragon-Tiger List institutional seat transaction details) and includes a source URL. This is clear enough to distinguish it from other stock_lhb_* sibling tools, though it lacks an explicit verb like 'get' or 'retrieve'. The Chinese title is specific and informative, so purpose is clear.

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?

The description gives no guidance on when to use this tool versus alternatives. There is no mention of use cases, context, exclusions, or alternative tools. It simply states the resource name and return type without any situational guidance.

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