macro_usa_new_home_sales

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to state safety. It adds the data range, source URL, and return type (pandas.DataFrame), which are useful. However, it does not disclose details such as the data's update frequency, seasonal adjustment, or that the tool returns the entire historical series without filtering.

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 front-loaded with the report name and data range. It includes a source URL and return type. However, the :return: phrase repeats the main title, which is slightly redundant and could be trimmed.

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 parameterless, read-only data report, the description is mostly complete: it gives the dataset, time span, source, and return type. The lack of an output schema is mitigated by the explained return type. It could be improved by stating the metric's frequency or units, but overall it is sufficient.

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 schema covers 100% of the (empty) parameter space, earning a baseline of 4. The description adds no parameter-specific information, but none is needed since there are no parameters to explain.

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 names the resource: '美国新屋销售总数年化报告' (US new home sales total annualized report) and specifies the data range (19700101-present). This distinguishes it from sibling tools like macro_usa_exist_home_sales and macro_usa_pending_home_sales, though it lacks an explicit action verb like 'fetch' or 'download'.

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?

The description provides no guidance on when to use this tool versus related macro indicators. It does not mention alternatives, prerequisites, or exclusion scenarios. An AI agent would have to infer usage from the tool name alone.

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