fund_aum_trend_em

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds the source URL and return type (pandas.DataFrame), but no additional behavioral details such as data frequency, update schedule, or scope. This is acceptable for a simple read-only tool, but the description itself adds minimal extra 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 short and includes the source URL and return type, but it is slightly redundant: the first line and the ':return:' line essentially repeat the same concept. It remains concise and front-loaded with the primary purpose.

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 the zero-parameter nature, rich annotations (read-only, idempotent, non-destructive), and simple DataFrame return, the description is nearly complete. It identifies the data source and return type. However, it does not describe the data shape or columns, which could be useful if the agent needs to interpret the DataFrame, but this is not critical for a no-param retrieval tool.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameter meanings. The input schema confirms no parameters, and the description's return mention is sufficient.

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 states the tool returns a fund market management scale trend chart from Eastmoney, which is specific and clear. However, it lacks an explicit verb like 'get' or 'fetch', and the phrase '走势图' is repeated in the return line. It does not distinguish itself from sibling tools such as fund_aum_hist_em or fund_aum_em.

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 guidance on when to use this tool versus alternatives. No mention of whether it covers the entire market, historical range, or how it differs from similar AUM tools. The description only states what it returns, not the context for selecting it.

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