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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real context beyond them: it declares the returned measures (mortgage count, UPB, units) and the monthly HUD snapshot provenance, plus a clear negative-capability list. It does not mention pagination or the limit/offset ceiling.

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?

Four tight sentences, front-loaded with the core action, followed by return shape, usage triggers, and exclusions. No filler and nothing redundant with the schema.

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 correctly carries the return-value burden (count, UPB, units, provenance) and marks the read-only scope. Remaining gaps are the undocumented pagination/filter parameters, which leaves the 7-param surface only partially covered.

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 43%, so the description should compensate but only partly does. It surfaces the group_by dimensions (holder/state/month) and the exact date window, but says nothing about the state filter, limit, offset, or response_format parameters.

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 opens with a specific verb+resource: 'Aggregate confirmed HUD FHA multifamily mortgage maturities,' and scopes it to by-holder/state/month over a date window. It implicitly contrasts with the sibling hud_fha_maturity_search via the 'Aggregate' framing, but never names that sibling, so differentiation is left to inference.

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?

It gives concrete trigger phrases ('which FHA lenders have maturities in 2027?', 'FHA maturity exposure by state') and an explicit exclusion list (no default risk, ownership, borrower intent, refinancing likelihood). It stops short of naming the alternative tool (hud_fha_maturity_search) for raw per-loan lookups.

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