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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds real value on semantics — it previews returned content (source project fields, unit counts, labeled screening date) and warns that year 15 does not imply affordability expiry. It still says nothing about pagination behavior or result volume, so it sits just above baseline rather than above it clearly.

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 the core operation, then returns, then the interpretive caveat — no repetition of the title or schema and nothing that could be cut without losing signal.

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 no output schema, the description responsibly describes the return payload and adds a domain caveat about extended-use rules, which matters for a housing-compliance query. Given rich annotations and fully documented parameters, only pagination/large-result guidance is left unaddressed.

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% with formats and examples for every parameter, so the baseline of 3 applies. The description only echoes the window concept and adds nothing about state, min_units, limit, offset, or response_format.

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 precise verb and resource with scope: 'Find HUD LIHTC properties whose placed-in-service year reaches the federal 15-year reference date in an exact window.' The role of the date parameters is concrete, but the description never contrasts itself with adjacent date-window tools in the sibling list (e.g. hud_fha_maturity_search, affordable_housing_refinance_evidence_pack), leaving disambiguation to the name alone.

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 "LIHTC projects reaching year 15 in 2027"' supplies a concrete triggering scenario, and the closing caveat frames what the result does and does not mean. There is no explicit when-not-to-use or named alternative, so the guidance is clear but not exhaustive.

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