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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: the two source sets are NOT property-matched (because FHA's workbook lacks a street-address key), and results never assert a refinance opportunity, contact, valuation, or expiration. Those negative claims are exactly the caveats an agent needs to avoid over-reading output. It does not describe the pack's internal structure, which keeps it from a 5.

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?

Three sentences, front-loaded with what the tool returns, then the use case, then the caveats. No filler. The final sentence is long and chains several negations, but each negation is load-bearing disclaimer content rather than padding.

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?

There is no output schema, so the description must carry the return-value burden, and it does so at a high level: source-linked, two distinct source sets, state-level, date-windowed, plus explicit limits on what is claimed. A short note on the pack's section layout (given the markdown/JSON response_format choice) would close the remaining gap.

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 every parameter (state, start_date, end_date, limit, response_format) is already documented with patterns and bounds. The description reinforces state-level and single-date-window scoping but adds no format, default, or edge-case detail beyond the schema. 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?

The first sentence names a specific verb (return), a specific artifact (state-level, source-linked evidence pack), and the exact source sets (HUD FHA maturity records + HUD LIHTC year-15 signals) with a date-window scope. That is far more specific than a tautology. It stops short of naming the sibling tools it combines (hud_fha_maturity_search, hud_lihtc_year15_radar), so an agent must infer the relationship rather than being told it.

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?

"Use this for affordable-housing debt or timing diligence" gives a real use-case context, which is more than nothing. However, it never states when to prefer this combined pack over the individual HUD tools in the sibling list, nor any exclusions or prerequisites. The routing decision between this and the two single-source tools is left to inference.

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