macro_bank_china_interest_rate

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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the safety profile is clear. However, the description adds only a return type and data range, and these are clouded by the contradictory country references. It does not clarify what the returned pandas.Series contains (e.g., actual interest rate values) or the source's intended scope.

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 fragmented and not front-loaded. It contains two long URLs that are unnecessary for tool selection, and the China/New Zealand mismatch introduces noise rather than clarity. The return type and rtype are repeated in an unstructured manner, making it difficult to parse at a glance.

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?

While the description provides a date range and return type, the contradictory semantics and lack of a clear description of the actual data content make it incomplete. The tool is simple (no parameters), but the description fails to communicate what the series represents, leaving an agent unable to correctly use or interpret the output.

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, so the input schema is complete by default. The description's mention of the date range and return type provides some context, but with zero parameters, there is little to explain. Baseline of 4 is appropriate given the vacuum.

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 is self-contradictory: it states '中国央行决议报告' (China central bank decision report) but then returns '新西兰联储决议报告-今值(%)' (New Zealand Fed decision report). This directly conflicting information makes the tool's true purpose ambiguous and misleading, preventing an agent from knowing what the tool actually does.

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. The description only gives a data range and return type, without any context on use cases, prerequisites, or exclusions. The presence of many similar sibling tools highlights the lack of differentiation.

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