rate_rangesIndicative starting rate by program, from the site's single rate source, stamped with its as-of month (currently October 2026). These are the published ranges, not pricing on any deal.
| Name | Required | Description | Default |
|---|---|---|---|
| program | No | Program key to filter to; omit for all. One of: dscr, dscr_cash_out, short_term_rental, fix_and_flip, ground_up, rental_portfolio, bridge, commercial |
Changes observed during successful MCP inspections.
Input schema / properties / program / descriptionPrevious value: -"Program to filter to: dscr, str, fixAndFlip, groundUp, portfolio, commercial, bridge"New value: +"Program key to filter to; omit for all. One of: dscr, dscr_cash_out, short_term_rental, fix_and_flip, ground_up, rental_portfolio, bridge, commercial"Input schema / properties / program / enumAdded value: +[
+ "dscr",
+ "dscr_cash_out",
+ "short_term_rental",
+ "fix_and_flip",
+ "ground_up",
+ "rental_portfolio",
+ "bridge",
+ "commercial"
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real value beyond them: data provenance (single rate source), a staleness signal (as-of month, currently October 2026), and the semantic caveat that these are indicative published ranges, not quotes.
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?
Two tight sentences, no filler, with the core capability front-loaded before the scope caveat. Every clause carries information the structured fields do not.
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?
For a read-only, zero-required-parameter lookup with no output schema and full schema coverage, the description supplies the interpretive context an agent needs (provenance, as-of date, indicative vs. deal pricing). It stops short of describing the shape of the returned ranges, a minor gap given no output schema exists.
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 a single enum parameter fully documented in the schema, so baseline 3 applies. The description's 'by program' phrase merely restates the filtering the schema already defines and adds no syntax or format detail.
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+resource: returns indicative starting rates by program from a single rate source. The second sentence explicitly scopes out deal-specific pricing, which helps an agent distinguish this from any pricing tool. However it never names or contrasts itself against siblings like loan_programs, so differentiation is implicit rather than explicit.
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 implied — an agent can infer you call this to look up published rate ranges. The caveat 'not pricing on any deal' functions as a scope guard rather than a when-to-use rule, and no alternative tool or condition is named. No explicit when/when-not guidance is present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.