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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered; the description adds useful context beyond that: the HMDA data provenance, recency ('latest federal data'), and ranking methodology. It does not discuss result ordering ties or empty-result behavior, but against the annotation baseline this is solid.

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?

Front-loads the resource definition and ranking logic, then lists return fields, then closes with example queries. Slightly dense, but every clause carries information; the return-field enumeration is the only mildly padded portion.

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 does the work of enumerating return fields (loans closed, market share, approval share, median loan, programs, HQ, health grade), which is exactly what an agent needs. It stops short of describing result structure or response envelope, keeping it just under complete.

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 80%, so the schema already documents nearly every parameter including the city fallback and lender_type semantics. The description restates the loan programs and lender categories but adds no format or edge-case detail beyond what the schema provides, so baseline 3 applies.

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?

Names a specific resource (mortgage lenders and brokers) and scope (U.S. state or city), states the ranking basis (home loans closed in latest HMDA data) and the data source (MonitorBankRates directory). This is clearly distinguishable from siblings like get_institution and search_institutions, which are generic institution lookups.

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 example queries ('best mortgage lenders in Florida', 'FHA lenders in Tampa', 'credit unions that do mortgages in Ohio') that map directly to the state/city/program/lender_type parameters, giving strong implied usage context. It does not explicitly say when to prefer this over siblings such as get_best_rates or search_institutions, so it falls short of a 5.

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