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

No annotations are provided, and the description gives no behavioral context—no mention of read-only, data source, time range, response format, or limitations. The phrasing is a noun-phrase tag rather than an explanation of what the tool returns or how it behaves.

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 a single, efficient sentence fragment that front-loads the subject and lists content areas without waste. Every word adds value.

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?

The description lists the data categories but omits crucial context such as time period, frequency, units, and output shape. Without an output schema or additional details, an agent cannot fully infer what the tool returns, making the coverage incomplete.

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 shows an empty object, so there are no parameter semantics to clarify. Per the rubric, 0 params yields a baseline of 4, and the description adds no irrelevant parameter 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 US housing market data, listing specific indicators like housing starts, permits, median prices, 30Y mortgage rates, and home sales. This distinguishes it from sibling tools focused on employment, inflation, and other sectors, despite lacking an explicit verb.

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 implies the tool should be used when housing market data is needed, but does not explicitly state when to use it compared to alternatives or exclude cases. No alternatives or exclusions are mentioned, leaving usage to inference.

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