macro_china_nbs_region

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. However, the description introduces a confusing instruction to set 'symbol' to None, which does not match any input parameter in the schema (which uses 'indicator'), potentially misleading an agent. It also omits details on rate limits or any other runtime constraints.

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 docstring is reasonably short and front-loaded with the title and URL. The parameter and return structure is logical, but the confusing 'symbol' reference serves as a distractor, and a quick example of a valid path and indicator would make it more actionable.

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?

As a generic interface with five parameters and no output schema, the description should explain valid path values, indicator formats, and the overall return structure. The current text only promises a pandas.DataFrame and leaves the agent to discover path/indicator conventions elsewhere, making it incomplete for confident invocation.

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 description defines all five parameters, including concrete period format examples ('LAST10', '2016-2023', '2016-') and the region/indicator interaction. While the 'symbol' wording is a minor inconsistency, the description adds substantial meaning beyond the bare schema, which is especially valuable given 0% schema coverage.

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 tool as the National Bureau of Statistics regional data general interface, with a direct data source link. It distinguishes itself from sibling tools like macro_china_nbs_nation by focusing on region-level data, although the verb 'retrieve' is implied rather than stated explicitly.

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 such as macro_china_nbs_nation or macro_cnbs. The description only lists parameters and return type, leaving the agent to infer the appropriate use case from the tool name.

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