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

With no annotations provided, the description carries the transparency burden. It discloses that the result is a historical observation from a public source, is not a prediction, and is not a recommendation, which are meaningful behavioral caveats for a lending-related tool. It infers a read-only list operation but does not explicitly state possible rate limits or other operational behaviors.

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?

The description is dense and front-loaded with intent and return contents, followed by scope limits and caveats. The ALL-CAPS formatting is a bit noisy, but every major piece earns its place: what it returns, what it excludes, data source, disclaimer, and attribution.

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?

Given that there is no output schema and no annotations, the description provides a good amount of needed context: return fields, ranking scope, data source, licensing, and non-prediction disclaimer. It is not fully complete because it never clarifies the semantics of the `limit` parameter, but overall it gives an agent enough guidance to call the tool for the intended use.

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 0%, so the description must compensate for the two parameters. It partially does by referencing 'denial rate' and 'volume' relevant to the sort enum and the 'top 100' ceiling relevant to limit, but it never explicitly explains the `sort` enum options or the default/effect of `limit`.

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 states a specific action and resource: 'Returns the ranked list of the 100 largest FHA lenders with name, slug, rate and volume.' It also presents concrete user questions it answers and explicitly lists what it is NOT for, which clearly distinguishes it from sibling statistical/analysis tools.

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?

The description gives clear when-to-use guidance through example questions and explicit exclusions ('NOT FOR: lenders outside the top 100, or any recommendation about where to apply'). It does not name specific alternative sibling tools, which prevents a 5, but the context makes the appropriate use fairly clear.

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