macro_china_new_house_price

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds the source URL and the return type (pandas.DataFrame), but does not disclose any additional behavioral traits such as rate limits, data freshness, or how the two city parameters affect the result. This is acceptable but not rich.

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 compact and follows a standard docstring format with title, URL, params, and return. It is front-loaded with the Chinese title and includes the source URL, which is useful. No unnecessary filler, though the param descriptions are minimal.

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?

With only two string parameters, simple annotations, and no output schema, the description should clarify what the tool returns and how the parameters work. It only states it returns the new house price index as a DataFrame, but does not explain the time period, geographic scope, or how the two city parameters are used. This is a significant gap for an agent attempting to invoke the tool correctly.

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?

Schema description coverage is 0%, so the description must compensate. It states that city_first and city_second are cities and directs users to the target website for a city list, which adds some meaning. However, it does not explain the relationship between the two cities (e.g., comparison, separate queries) or provide any domain-specific guidance on valid values, leaving the agent with insufficient information.

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 providing China's new house price index, with a data source URL and a return type of DataFrame. However, it lacks an explicit verb like 'fetch' or 'retrieve', and does not distinguish itself from the many other macro_china_* tools beyond its name.

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 provides a data source URL and param/return documentation, but does not mention any exclusions, prerequisites, or comparison to sibling tools like macro_china_real_estate or macro_china_house_price_index.

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