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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuine beyond-schema context: the content is 'as hospital.loans publishes them, with citations,' which tells the agent the authority and traceability of the answer. It stops short of stating freshness/version or that the content is static reference material.

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 dense sentence that front-loads the source and scope, then lists the four coverage areas in the same order as the topic enum. Every clause maps to a queryable topic; it is long but not padded.

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 carries the burden of describing returns, and it does so thoroughly for all four topic values. Combined with a fully documented two-parameter schema and complete annotations, an agent has everything needed to call this correctly and know what to expect.

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% and both enums are already documented in the schema, so the baseline is 3. The description still adds value by spelling out the substance behind each topic (the four programs with limit/term/MIP, the 24 CFR tests, fees/reserves, process days) and by confirming the program parameter's role in narrowing topic=programs.

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 names a specific resource (HUD hospital mortgage insurance rules) and enumerates exactly what it covers: the four programs, Section 242 eligibility tests, fees/reserves, and process steps. It is distinguishable from the siblings (get_hospital, search_hospital_loans, get_portfolio_stats) by being a rules reference rather than a data lookup, though it never says so explicitly.

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: an agent can infer this is the tool for 'what are the rules' questions versus loan/hospital data tools. There is no explicit when-to-use, when-not-to-use, or named alternative, so nothing actively routes the agent away from a sibling.

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