stock_margin_detail_sse

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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) already establish the safety profile. The description adds the return type (pandas.DataFrame) and source URL, but does not disclose behavior like date format constraints, pagination, or data availability.

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 brief and front-loaded with the title and URL, followed by parameter documentation in a standard docstring format. No unnecessary words, though it could be more narrative.

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?

For a simple one-parameter data retrieval tool, the description adequately states the source, return type, and basic parameter meaning. However, it lacks usage differentiation from sibling tools and does not mention any caveats about data format or availability, making it minimally viable but not comprehensive.

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 no description for the 'date' parameter (0% coverage), so the description must compensate. It does add the semantic label '交易日期' and type 'str', but stops short of explaining the expected format (e.g., YYYYMMDD), relying on the default value as an example.

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 identifies the resource (SSE margin trading detail) and provides a source URL, distinguishing it from similar tools for other exchanges (SZSE/BSE). However, it lacks an explicit verb like 'get' or 'list', relying on the noun phrase '融资融券明细' to convey the action.

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 guidance is provided on when to use this tool instead of siblings such as stock_margin_sse or stock_margin_detail_szse. The description does not mention exchange-specific scope or prerequisites, leaving the agent to infer usage solely from the name.

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