fund_announcement_report_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 only the return type (pandas.DataFrame of an announcement list); it says nothing about date coverage, pagination, or result ordering that annotations do not provide.

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?

Compact and front-loaded with the resource identity, source site and URL. The Sphinx :type/:rtype lines are mildly redundant, but overall there is little wasted text.

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 read-only tool with no output schema, the description covers the input and the return shape, and annotations cover safety. It stops short of clarifying result scope (which reporting periods, how many rows, sorting), which an agent might need.

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 burden, and it does: symbol is the fund code, with a pointer to ak.fund_name_em() for discovery. That is meaningful guidance beyond the bare string type in the schema, though it omits format details (e.g. length/zero-padding).

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 a specific verb+resource: periodic report announcements from the East Money / TianTian fund archive (基金公告-定期报告), and even gives the source URL. This partially distinguishes it from siblings like fund_announcement_personnel_em and fund_announcement_dividend_em via '定期报告', though it never explicitly contrasts them.

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 such as fund_announcement_dividend_em or fund_announcement_personnel_em. The only procedural hint is that the symbol can be obtained via ak.fund_name_em(), which helps obtain a parameter but not choose the tool.

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