Margin Trade

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

No annotations are provided, so the description carries full burden. It only states the basic function of getting data, without disclosing behavioral traits such as read-only nature, rate limits, authentication requirements, or error handling. This is insufficient for a tool with multiple parameters and data types.

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?

A single sentence that is concise and front-loaded with the main purpose. It efficiently lists supported data types, though a bulleted list could improve readability. 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?

The tool has 5 parameters and no output schema. The description does not explain return values, pagination, or how to interpret the data types. For a data retrieval tool, this is a significant omission, leaving the agent without guidance on what to expect from the response.

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 100%, so baseline is 3. The description adds a high-level categorization of data types ('融资融券标的股票、交易汇总、交易明细等'), which helps group parameters but does not add syntax or format details beyond what the schema already provides for each parameter.

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 margin trading data ('获取融资融券相关数据') and lists multiple data types (标的股票、交易汇总等). The title 'Margin Trade' aligns. It distinguishes from sibling tools by focusing on a specific financial domain not covered by others like basic_info or stock_data.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for margin trading data, but it does not mention when not to use it or suggest other tools for related data needs.

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