fund_fh_em

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 one behaviorally useful detail not in the schema: page=-1 means fetch all pages. Beyond that it only restates parameter types, so 3 is appropriate.

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 resource is front-loaded and the per-parameter docstring format is scannable, but the raw page URL and the duplicated Chinese title line add noise, and the long enum lists make it bulky. It is thorough rather than concise.

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?

Given five all-optional parameters, zero schema coverage and no output schema, the description supplies the enum vocabularies and defaults needed to call the tool correctly. It notes the return is a pandas.DataFrame but doesn't describe columns, which is acceptable with no output schema.

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 no enums are declared in the schema, so the description carries the full burden. It documents all five parameters, and crucially enumerates the accepted values for typ (~26 fund categories), rank (six sort fields with Chinese expansions) and sort, which the schema alone would not convey.

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 source (天天基金网), the resource (基金分红/fund dividends) and the page URL, so the agent can tell it is a dividend-distribution data fetch. It lacks an explicit verb and doesn't name the closest siblings (fund_fh_rank_em, fund_announcement_dividend_em, fund_etf_dividend_sina), so disambiguation is left to the agent.

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 statement of when to use this tool versus alternatives, no prerequisites, and no mention of sibling dividend tools. Usage is only implied by the parameter list (year/type/ranking).

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