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

Annotations already cover read-only, idempotent, non-destructive, open-world, so the bar is lower; the description still adds provenance ('HUD's monthly FHA Subsidiary Ledger extract') which implies an update cadence, and enumerates the return payload. It does not quantify staleness of the monthly extract or any rate/row constraints beyond what the schema says.

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 dense sentences, front-loaded with the operation and window semantics, then filters, then the return payload and the disambiguation caveat. Every clause carries information; the only friction is the unexplained 'HUD TC' abbreviation alongside LIHTC.

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?

No output schema exists, and the description compensates by naming the returned fields (property, project number, maturity, balance, units, lender, rate, provenance). With 9 params all documented and the source dataset identified, the only residual gap is refresh cadence of the monthly ledger.

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 coverage is 100% so the baseline is 3, but the description maps filters to intent (state, holder/lender name, unpaid balance, HUD TC/LIHTC) and clarifies that min_balance is about unpaid principal rather than original loan amount. Minor wording drift ('holder-name' vs the schema's 'lender') is the only ambiguity.

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 verb and resource — 'Find official HUD active multifamily FHA mortgages maturing in an exact window' — plus the filterable dimensions and returned fields. It also draws a sharp semantic boundary ('a maturity is a filed source field, not refinance intent or a contact lead list') that separates it from adjacent products like hud_fha_lender_exposure or hud_lihtc_year15_radar without naming them.

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?

Provides concrete triggering queries ('FHA loans maturing in Texas next year', 'multifamily debt maturity schedule') and a negative boundary (not refinance intent, not a contact/lead list). It stops short of naming sibling tools as explicit alternatives or stating when another tool would be the better pick, so it is clear context rather than full routing.

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