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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real context beyond them: the data is a static snapshot captured on a specific date ('read 2026-10-24'), sourced from each lender's own website, and includes exact source pages for verification. It omits any note on how stale data should be treated or what a miss looks like.

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?

One front-loaded sentence that states what is returned, the source, and the capture date before the field list, with zero filler. The enumeration, while long, earns its place by telling the agent exactly what coverage to expect.

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, but the description compensates by enumerating the returned fields (rates, leverage, points, terms, credit rules, loan sizes, states, license, notes, source pages). Combined with annotations covering the safety profile and the description covering provenance and freshness, an agent has enough to call it correctly; only the failure/empty case is unaddressed.

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 the single 'lender' parameter already carries example values (Kiavi, Lima One, RCN Capital). The description contributes only the framing that the name identifies a lender whose own site was scraped, which adds little beyond the schema; 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?

States a specific verb and resource ('Everything fixandflip.loans recorded from one lender's own website') and enumerates the exact fields returned, so an agent knows this is a single-lender detail lookup rather than a search. It does not explicitly name siblings like find_lenders or compare_lender_costs, so the differentiation is implied by 'one lender' rather than stated.

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: the phrasing and the required 'lender' parameter make it clear this is for pulling detail on a lender you already have a name for, but there is no explicit when-to-use, when-not-to-use, or pointer to the sibling search/compare tools. An agent must infer the routing from context.

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