macro_bank_china_interest_rate

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description adds the useful historical coverage window (1999-01-05 onward) and the unit of the returned value (%), but nothing about auth, rate limits, or update cadence. No contradiction with the annotations themselves.

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 text is a raw docstring dump: a header line followed by two unfiltered source URLs, one with a cache-busting query string, plus Sphinx-style :return:/:rtype: tags. The URLs add no decision-relevant information for an agent and dilute the one useful fact (the date range).

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?

There is no output schema, and the description partially compensates by giving :rtype: pandas.Series and the value unit (%), plus the historical window. However, the conflicting country metadata (China in the title/name, New Zealand in the URLs and return tag) leaves the actual returned series ambiguous.

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 zero parameters (empty schema), so there is no parameter semantics for the description to supply. Baseline 4 applies.

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 first line names a resource and scope (China central bank decision report, 1999-01-05 to present), but the body then embeds two URLs for 'dc_newzealand_interest_rate_decision' and ends with ':return: 新西兰联储决议报告-今值(%)', pointing at New Zealand rather than China. The agent cannot tell whether this tool returns China or New Zealand policy-rate 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?

There is no guidance on when to use this tool versus the many sibling rate tools such as macro_bank_newzealand_interest_rate, macro_china_lpr, or macro_bank_usa_interest_rate. It also does not state whether any arguments or preconditions are needed.

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