macro_china_shrzgm

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the source URL and return type (pandas.DataFrame), which is useful, but it does not disclose data granularity, update frequency, or potential scraping/network behavior. It does not contradict annotations.

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 appropriately short, containing a title, URL, and docstring-style return info. It is front-loaded with the title, but there is no explanatory sentence about the data itself. It is concise with no wasted words, yet slightly under-specified.

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 no-parameter retrieval tool, the description gives the source and output type, but it omits what columns, time periods, or data granularity the returned DataFrame contains. Since there is no output schema, the description should provide more detail about the returned data to be fully 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 has zero parameters and the input schema is empty with 100% schema description coverage. Per the rubric, the baseline for 0 parameters is 4, and the description does not need to add parameter details since none exist.

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 names the specific resource (社会融资规模增量统计) and provides the source URL, making clear it returns social financing scale increment statistics. However, it lacks an explicit verb like 'fetch' or 'get', and does not explicitly differentiate from sibling macro tools, though the title is specific enough to imply the 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?

There is no guidance on when to use this tool versus alternatives such as macro_china_money_supply or macro_china_pmi. The description does not mention data coverage, update frequency, or any prerequisites, leaving the agent without context for selection.

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