hurun_rank

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious substance on top: it cites the source site URL and gives per-indicator valid year ranges (e.g. 胡润全球富豪榜 2019-至今), which is behavioral constraint info not present in annotations or schema.

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 sphinx-style :param:/:type:/:return: boilerplate is redundant with the input schema, and a raw source URL is placed near the top ahead of any usage guidance. The content is useful but not tightly front-loaded, and the indicator-to-year mapping is duplicated in a second list.

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?

For a two-parameter, no-output-schema tool, the description covers both parameters well, states the return is a pandas.DataFrame, and gives the source for verification. The remaining gap is the internal inconsistency between the indicator list and the year-range map, which could mislead an agent choosing an indicator.

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 description coverage is 0% and the schema declares no enums, so the description carries the full burden — and it delivers, enumerating the valid indicator values and the valid year span per indicator. It falls short of 5 because the default values ('2023', '胡润百富榜') and expected string format are never explained, and the year map references '中国瞪羚企业榜' which is absent from the indicator list.

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 a specific resource (胡润排行榜 / Hurun rankings) and enumerates the nine distinct ranking indices the tool can return, so the agent knows exactly what data domain this covers. It is clear enough to distinguish from most siblings, but it never names or contrasts with adjacent ranking tools like forbes_rank or index_bloomberg_billionaires.

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 only implied: the indicator list signals which datasets exist, but there is no when-to-use statement, no exclusions, and no pointer to alternative ranking tools (forbes_rank, xincaifu_rank). The agent must infer the conditions from the enum values alone.

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