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

Annotations only say read-only and closed-world; the description adds the substantive rules an agent can't infer: free, a 200-row cap, newest-first ordering, a specific queue priority order (covered groups since July 11 2026, lenders removed, no-BTR-signal first, bulk restructurings last), and the Jan 7 2027 violation threshold. That is exactly the beyond-annotation context this dimension rewards.

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?

Content is dense but nearly all of it earns its place; the problem is form, not volume. It reads as one long semicolon-chained block, so the enumeration of signals and queue-ordering rules is hard to scan and easy to mis-parse.

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 an 8-param, free-text-filter tool with no output schema, it covers filtering, ordering, caps, and domain rules well. It does not say what fields each row contains or how to page past 200 rows, which an agent will want before relying on it.

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?

With 0% schema coverage across 8 params, the description carries the load and mostly succeeds: group, county, status, since (YYYY-MM-DD), queue, vehicles, and the full signal vocabulary are all explained, including non-obvious codes like BULK_SAME_DAY_TRANSFER. Only 'limit' and the accepted values for 'status' / format of 'group' are left implicit.

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 resource with scope: recorded deeds (last sale per parcel, county rolls) streamed into 350+ home groups, newest first, plus a distinct 'agency case queue' mode. An agent knows what data comes back and in what order. It stops short of naming how it differs from siblings like road_screen_purchase or road_investor_group.

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?

Mode-selection guidance is explicit: queue=true switches to the enforcement queue, vehicles=true switches to Texas registry vehicles, and the signal list names the situations to filter on. What's missing is routing guidance against siblings (e.g., when to screen a single purchase instead of streaming).

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