macro_china_market_margin_sz

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context about the data range, source URL, and return type (pandas.DataFrame), but does not disclose additional behavioral traits such as update frequency, rate limits, or pagination. Since annotations cover the core safety aspects, a score of 3 is appropriate.

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, consisting of three short pieces of information: the report name, data range, source URL, and return type. Each line serves a purpose, though the structure is a bit fragmented (with a raw URL and an explicit ':return:' line). For a simple tool, this is acceptable and not verbose.

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 zero-parameter, read-only tool with no output schema, the description provides the essential facts: what the report contains (Shenzhen margin trading), the date range, the data source URL, and the return type. It does not mention data frequency or specific columns, but given the simplicity of the tool and the presence of annotations, this is reasonably complete.

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 tool takes no parameters, and the input schema is an empty object. The description does not need to explain parameter semantics, and there is no parameter information missing. The baseline of 4 for zero-parameter tools is appropriate because the schema fully covers the parameter space, and the description adds clarity about the return type and data range.

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 as '深圳融资融券报告' (Shenzhen margin trading report) and specifies the data range (from 20100331 to present). It distinguishes itself from likely sibling tools like macro_china_market_margin_sh by region. However, it lacks an explicit action verb such as 'retrieves' or 'fetches', relying on the noun phrase to convey purpose.

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 versus alternatives. It does not mention that this is specifically for Shenzhen data or refer to the Shanghai counterpart. The description only states what the report is and gives a source URL, with no contextual advice for selection.

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