macro_usa_spcs20

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations — the data range (20010201-present), the jin10 source URL, and that the return is a pandas.DataFrame — which is genuine added value but stops short of describing update cadence or column shape.

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 content is compact and front-loaded with the resource name and data range, which is the most useful information. It is slightly redundant, as the ':return:' line restates the description text verbatim, wasting a line.

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 macro-data tool with annotations carrying the safety profile and no output schema, the description supplies the essentials: topic, historical coverage, source link, and return type. It lacks only minor operational details such as publication frequency, which is not critical to 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 tool takes zero parameters, so there is nothing for the description to document and schema coverage is moot. Baseline 4 applies; no parameter semantics are needed here.

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 names a specific resource — the US S&P/CS20 Case-Shiller large-city home price index annual-rate report — which is distinguishable from siblings like macro_usa_house_price_index and macro_usa_phs. However, it uses a noun phrase ('报告') rather than an explicit verb and does not explicitly differentiate itself from those closest siblings.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer for related US housing indicators (e.g., macro_usa_house_price_index, macro_usa_nahb_house_market_index). The agent must infer usage entirely from the topic name.

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