xincaifu_rank

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the safety profile is covered. The description adds the useful temporal scope (data from 2003 to present) and the return type (pandas.DataFrame), which is genuine extra context beyond the 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 name and source URL are front-loaded, which is good, but the Sphinx-style :type/:rtype lines restate what the schema and return convention already imply, adding boilerplate. It is not bloated, but not every line earns its place.

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 simple one-parameter read tool with no output schema, the description covers purpose, source, valid year range, and return type. What it lacks is routing guidance against the many sibling ranking tools, which is the main missing piece.

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%, so the description must carry the parameter. It does explain that 'year' is the specific ranking year and that valid data spans 2003 to the present, which meaningfully constrains acceptable input even though the string format is only implied by the schema default.

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 names the resource (新财富500人富豪榜) but largely restates the tool title without an explicit verb, so it reads as a label rather than a described action. It does add identifying context (the source URL and the 2003-present data window), but it never distinguishes itself from close siblings like forbes_rank, hurun_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?

There is no guidance on when to use this tool versus alternatives. With several near-identical rich-list tools in the sibling set (forbes_rank, hurun_rank, index_bloomberg_billionaires), the absence of any disambiguation is a real gap.

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