macro_usa_pending_home_sales

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the data start date and a source URL, which is useful context, but does not disclose update frequency, data granularity, or any other behavioral traits beyond what annotations provide.

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 short but redundant: the phrase '美国成屋签约销售指数月率报告' appears twice, and the :return line repeats the title. The URL and rtype are useful, but the repetition wastes space and could be streamlined.

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 zero-parameter data retrieval tool, the description is fairly complete. It states the report type, data range, and return type (pandas.DataFrame). There is no output schema, but for a simple time-series report, this level of detail is adequate. It could mention update frequency or column structure, but those are not critical for basic use.

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, so the schema trivially covers 100% of parameters. According to the rubric, 0 parameters merits a baseline score of 4. The description adds no parameter information because there is nothing to add.

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 resource as the US pending home sales index monthly rate report with a specific data range. It lacks an explicit verb like 'get' or 'retrieve', but the tool name and description make the function obvious. It is distinguishable from siblings like macro_usa_exist_home_sales by the metric name and the report type.

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 alternatives such as macro_usa_exist_home_sales or macro_usa_new_home_sales. It only states the data range and return type, leaving the agent to infer usage from the name alone.

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