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

Annotations already declare readOnlyHint, non-destructive and a closed world, so the safety profile is covered. The description adds value beyond that by disclosing the cost ('Free') and enumerating exactly what the payload covers (deeds since 2025, vehicle registrations with no homes, 25 most recent purchases). The one gap is that it never says what happens when the name matches nothing.

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?

A single front-loaded sentence that establishes the lookup key first, then enumerates return content for a tool with no output schema. The long enumeration earns its place because nothing else documents the response, and there is no filler or repetition.

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?

Because there is no output schema, the description must describe returns, and it does so thoroughly, including the full ROAD Act status vocabulary. What remains missing is small: a not-found behavior and a pointer to the sibling tools that cover monitoring or purchase screening.

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 a single parameter at 0% schema description coverage, the description carries the full burden and does so: it states the 'name' argument accepts a group name, any member LLC name, or a group id, which the bare string schema does not convey. It stops short of describing matching behavior such as partial-name or case handling.

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 resource and scope: a single investor/control group keyed by group name, member LLC name, or group id, returned with county-level home holdings and ROAD Act status. It is far more specific than the title alone, though the underlying verb is implied rather than stated and no sibling tool is named to disambiguate it from road_screen_purchase or who_owns_home.

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: supply a group name or id when you want that group's profile and ROAD Act classification. There is no explicit when-to-use versus when-not-to-use guidance and no mention of the related road_* siblings, so an agent must infer the boundary itself.

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