fund_announcement_report_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing a safe read-only operation. The description adds the source URL and DataFrame return type, but does not disclose pagination, rate limits, or error behavior, providing only modest beyond-annotation context.

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 is a structured docstring with source, parameter, and return sections. It is concise and front-loaded with the category, though the first line essentially repeats the tool title and URL, which adds minimal value.

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 single-parameter tool, the description covers the source, parameter, and return type, but lacks details on the returned DataFrame columns and any potential caveats. Since there is no output schema, the vague '定期报告-公告列表' leaves ambiguity about the actual data structure.

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?

The schema has no descriptions (0% coverage), so the description's explanation of 'symbol' as the fund code and its pointer to ak.fund_name_em() for obtaining valid values is essential and effective. It compensates for the schema gap, though it does not include format examples beyond the default value.

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 states this tool retrieves periodic report announcements from Eastmoney's fund page, specifying the source URL and DataFrame return type. It distinguishes from sibling tools like fund_announcement_dividend_em and fund_announcement_personnel_em by the '定期报告' (periodic report) keyword, though it lacks an explicit verb like 'fetch' or 'list'.

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 gives a useful hint to obtain the fund code via ak.fund_name_em() and indicates the return type. However, it does not explicitly state when to choose this tool over other announcement types or provide any exclusions, relying mainly on the tool name and category for usage context.

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