fund_rating_sh

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 only that the return is a pandas.DataFrame and that the date comes from the source page; it does not note the default date behavior or any rate/coverage limits.

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?

It is short, but the raw source URL and Sphinx-style directives make it feel like scraped docstring boilerplate rather than a front-loaded statement of what the tool returns.

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 one-parameter, read-only lookup with no output schema, this is minimally adequate: it identifies the rating agency and the DataFrame return type. Missing date-format guidance and sibling differentiation are the main gaps.

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% for the single date parameter, so the description must carry the burden. Its note ('日期；<url> 获取查询日期') only vaguely says it is a query date and never states the expected format (the schema default 20230630 implies YYYYMMDD), leaving the agent to guess.

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?

Names a specific source and resource: East Money's fund rating page for Shanghai Securities (上海证券评级), which is more precise than a bare title. However, it never distinguishes itself from the closely related siblings fund_rating_zs, fund_rating_ja, or fund_rating_all, so the agent must infer the difference from the agency name alone.

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 when-to-use guidance and no mention of the alternative rating tools in a list crowded with fund_rating_* siblings. The only indirect hint is the source URL.

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