fund_rating_sh

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the source URL and return type (pandas.DataFrame) but no additional behavioral context such as rate limits, pagination, or data freshness. It does not contradict 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 follows a structured docstring format with title, URL, param, and return sections. However, the URL appears twice (in the title line and in the param description), which is redundant. It is compact but not maximally efficient.

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?

The tool has a single optional parameter, no output schema, and the description only states that the return is '上海证券评级' (Shanghai Securities rating) as a DataFrame. It does not specify the columns or data granularity, but given the low complexity and the annotations covering safety, this is minimally viable yet leaves some 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?

With 0% schema description coverage, the description partially compensates by explaining the 'date' parameter as '日期' (date) and directing the user to the URL for query date reference. However, it does not explicitly state the expected format (though the default '20230630' implies YYYYMMDD), leaving some ambiguity.

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 clearly identifies the resource as '天天基金网-基金评级-上海证券评级' (Eastmoney fund rating - Shanghai Securities rating) and provides the source URL. While it lacks an explicit verb like 'fetch' or 'get', the intent is unambiguous and it is distinguishable from sibling tools like fund_rating_zs or fund_rating_ja by the 'sh' suffix and Chinese title.

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 provides no guidance on when to use this tool versus the sibling rating tools (e.g., fund_rating_all, fund_rating_ja, fund_rating_zs). It does not mention alternatives or exclusions, leaving the agent to infer usage solely from the name.

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