get_hs300_stocks

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

With no annotations provided, the description carries full burden. It discloses the tool's read-only nature through 'fetches' and describes the return format (Markdown table or error message), but lacks details about data freshness, rate limits, authentication requirements, or error conditions beyond the generic 'error message' mention. The behavioral disclosure is adequate but minimal.

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 efficiently structured with a clear purpose statement followed by dedicated Args and Returns sections. Every sentence adds value: the first establishes context, the second explains parameter behavior, and the third defines output format. There's no redundant or 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?

Given the tool's moderate complexity (single optional parameter), no annotations, and the presence of an output schema (implied by 'Has output schema: true'), the description is reasonably complete. It covers purpose, parameter usage, and return format, though additional context about data sources or limitations would enhance completeness for a financial data 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 schema has 0% description coverage for its single parameter, but the description compensates by clearly explaining the 'date' parameter's purpose, format ('YYYY-MM-DD'), optional nature, and default behavior (uses latest if None). This adds significant semantic value beyond the bare schema, though it doesn't cover edge cases like invalid date formats.

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 specific action ('fetches') and resource ('constituent stocks of the CSI 300 Index'), distinguishing it from sibling tools like get_sz50_stocks and get_zz500_stocks which target different indices. It precisely defines the scope as retrieving index constituents rather than individual stock data or other financial metrics.

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 CSI 300 constituents, but provides no explicit guidance on when to use this tool versus alternatives like get_all_stock or get_stock_basic_info. It mentions the optional date parameter but doesn't explain scenarios where date specification is necessary versus using the default latest date.

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