stock_zygc_em

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds that it returns a pandas DataFrame and specifies the data source URL, but does not disclose any additional behavioral traits such as rate limits, data freshness, or error handling.

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 concise, including a purpose statement, source URL, parameter definition, and return type in a few lines. It is not overly verbose, though the docstring format is slightly unstructured.

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 simple one-parameter read-only nature and no output schema, the description provides enough to invoke the tool and understand its return type. However, it lacks specifics about the DataFrame columns or content beyond the generic '主营构成', which would help an agent know what to expect.

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 provides only the parameter name and default, with no description. The description compensates by explaining that 'symbol' is a stock code with market identifier, and the URL example (SH688041) further illustrates the format. This adds meaningful semantics beyond the schema.

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 the tool retrieves main business composition data from Eastmoney for a given stock, providing a specific resource and return type. While it doesn't explicitly differentiate from sibling stock tools, the purpose is clear enough from the Chinese title and docstring.

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 implies usage when needing main business composition for a stock, but gives no explicit guidance on when to prefer this tool over alternatives or any exclusion criteria. There is no mention of alternatives.

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