get_sz50_stocks

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

With no annotations provided, the description carries the full burden. It discloses the return format (Markdown table or error message) and default behavior (uses latest date if none provided), which adds useful context. However, it lacks details on rate limits, authentication needs, or error conditions beyond the generic mention.

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 Args and Returns sections. Every sentence adds value without redundancy, and it's front-loaded with the core functionality. No wasted words.

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 low complexity (1 optional parameter) and the presence of an output schema, the description provides sufficient context for basic use. It covers purpose, parameter semantics, and return format, though it could benefit from more behavioral details like error handling or performance expectations.

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 description coverage is 0%, but the description fully documents the single parameter 'date', including its optional nature, format ('YYYY-MM-DD'), and default behavior (uses latest if None). This compensates well for the lack of schema documentation, though it doesn't explain potential constraints like valid date ranges.

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 SZSE 50 Index'), distinguishing it from siblings like get_hs300_stocks and get_zz500_stocks which fetch different indices. It precisely defines the scope without ambiguity.

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 for retrieving SZSE 50 Index constituents, but does not explicitly state when to use this tool versus alternatives like get_all_stock or get_stock_basic_info. No exclusions or prerequisites are mentioned, leaving some context gaps.

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