macro_usa_exist_home_sales

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds the historical coverage (1970 onward), a source URL, and the return type, but does not disclose update cadence, data revision behavior, or returned columns. No annotation contradiction.

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 and front-loads the dataset name and date range. Some redundancy exists because :return: restates the purpose and the title repeats the first phrase, but there is no significant bloat.

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 simple no-parameter data-retrieval tool with annotations covering safety, the description gives the dataset and date range. However, no output schema exists and it only names pandas.DataFrame as the return, without listing columns, update frequency, or other return-shape details an agent might need.

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 the baseline is 4. The empty schema is fully covered (vacuously), and no additional parameter semantics are required or provided.

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?

States the specific dataset (US existing home sales annualized report) and its temporal coverage (19700101–present), which distinguishes it by name from siblings like macro_usa_new_home_sales and macro_usa_pending_home_sales. It does not explicitly contrast itself with those siblings, so it falls short of a 5.

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 identifies what the dataset is but gives no when-to-use guidance or alternatives. It does not say when to choose this over macro_usa_new_home_sales, macro_usa_pending_home_sales, or other housing indicators.

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