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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the history=true switch between a single period and the full monthly series, which is genuinely useful behavioral context, but it says nothing about pagination, data recency, or response shape beyond what the schema already covers. Adequate but not rich given the low bar set by annotations.

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?

Two tight sentences, front-loaded with the core action and scope, then the key behavioral flag, then the sibling routing. No filler or redundancy.

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 single-record lookup it covers what the tool does, how to select the record, the one behavioral toggle, and where to go for region discovery. With a full output schema and complete parameter descriptions, nothing an agent needs to invoke it correctly is missing.

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?

Schema description coverage is 100%, so all five parameters are already documented in the schema, including the period, history, and property_type defaults. The description restates the region_type/table_id keys and the history flag without adding format or edge-case detail beyond the schema, so the baseline 3 applies.

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 a specific verb and resource ('Fetch one stored US housing-market record') and immediately scopes it by the identifying keys ('by region type and Redfin table ID'). An agent can distinguish it from the facets and search siblings without opening any schema.

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?

Explicitly routes the agent to datasets_housing_markets_search 'to discover or filter regions,' clarifying that this tool is a single-record lookup requiring known IDs. It gives a clear positive alternative but stops short of stating exclusions (e.g. that it cannot list or browse) or prerequisites for the IDs.

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