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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavioral context the annotations do not: the dataset has no sale prices, days on market or sell-through rates because Texas does not disclose them, which stops an agent from requesting nonexistent metrics. It does not discuss result volume limits or how unmapped leads are reported.

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 sentences, front-loaded with the ranking action and with the data-limitation caveat placed last as a qualifier. Every clause carries information; nothing is restated from the name or annotations.

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?

With a full output schema, complete parameter documentation and rich read-only annotations, the description only needs to frame the metric set and its limits — which it does, covering lead tiers, transfer windows, buyer-type shares and the missing price/DOM data. Nothing an agent needs to call this correctly is absent.

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 the schema already documents all seven parameters, including min_score's default and the Tier A = 45+ threshold. The description reinforces semantics ('all tiers and Tier A', the 3/6/12/24-month windows, entity/absentee/out-of-state buyer share) but adds little the schema does not already say, so the baseline of 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?

The description names a concrete verb and resource: rank ZIP codes in Dallas or Collin County by tax-delinquent lead supply and owner-transfer activity. Its aggregate, ZIP-level scope is unmistakably different from the property-level siblings (get_property, filter_properties, search_properties), so an agent can route to it without opening a 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?

Usage is implied rather than stated: the description makes clear this is a market-overview / ZIP-comparison tool, and the 'no prices, days on market or sell-through rates' note usefully tells the agent what it cannot get from it. It never explicitly says when to pick this over siblings like filter_properties or motivated_sellers_near, or when to pass county versus zips.

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