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

It provides crucial operational traits not covered by annotations: the external source (fixandflip.loans), the data freshness/cut-off date (read 2026-10-24), and the specific fallback behavior ('check') when a lender publishes no state list.

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 perfectly sized. It is highly efficient, front-loading the data source and specific attributes without unnecessary filler.

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 the detailed schema and clear annotations, the description provides all necessary context—source, scope, data attributes, and error/edge case handling—making it maximally complete for this tool.

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?

Since schema coverage is 100%, the baseline is 3. However, the description significantly improves semantic understanding by detailing the specific data points returned for each lender (starting rate, leverage, etc.), giving the agent context about the quality and type of data found.

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 clearly states the goal: listing hard-money and DSCR lenders. It specifies the resource (fixandflip.loans) and distinguishes this tool's function from sibling tools by focusing on lender discovery rather than calculation or specific term retrieval.

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?

While it doesn't explicitly list alternatives, the context of 'finding' lenders implies it should be used when a list of providers is needed, effectively differentiating it from tools focused on calculation or comparison of terms.

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