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

Annotations already establish this is a read-only, idempotent, closed-world, non-destructive check, so the safety profile needs no restating. The description adds the substantive point that eligibility is judged against published agency criteria, but it omits key behavioral facts: what happens when the optional liquidity/net_worth/occupancy inputs are omitted, and whether the screen fails soft or reports insufficient data.

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 with no filler, naming the resource and the three criteria sets first. It is efficient, though borderline terse for a screening tool whose result interpretation matters.

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 eight parameters, no output schema, and no explanation of what the screen returns (per-program pass/fail, failing thresholds, or a list of shortfalls), the description leaves an agent unable to anticipate the response. It also never clarifies that four parameters are optional or what omitting them means for the verdict.

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 all eight parameters are already documented and the baseline of 3 applies. The description adds no domain nuance — neither what 'units' vs 'occupancy_months' drive in the criteria, nor how the optional sponsor metrics change the outcome when absent.

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?

Specific verb ("screen") plus the exact criteria sources (Fannie Mae Small Loans, Freddie Mac Conventional Small, HUD 223(f)), which tells an agent precisely what decision is being evaluated. It does not, however, say how this differs from siblings like match_programs or compare_programs, so the boundary 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?

Usage is only implied: 'screen a deal' suggests a pre-application eligibility check, but there is no explicit when-to-use, when-not-to-use, or routing to match_programs/compare_programs. An agent can guess the context but cannot rule out calling the wrong sibling.

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