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

Annotations already declare this a safe, read-only, idempotent, closed-world operation, so the description needn't repeat that. It adds context annotations cannot: the rates come from lenders' own websites read on 2026-10-24 (a data-freshness caveat), that results are ranked by profit, and that leverage, points and fees are held constant across lenders. It does not mention lender coverage or what happens when no lender matches the state filter.

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 dense sentences that lead with what the tool produces and its ranking criterion before covering the optional filter. Nothing is wasted, though the parenthetical '(plus those to check)' is slightly cryptic and the second sentence carries less weight than the first.

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 16 parameters, no output schema and read-only annotations, the description carries the burden of describing the result, and it does: interest cost, total financing and profit per lender. It also flags rate provenance and date. What's missing is what the comparison does when a lender cannot fund the deal (e.g. LTC/ARV cap failures), which matters for a 16-parameter comparison 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?

Schema description coverage is 100%, so all 16 parameters are already documented with defaults, ranges and examples; the baseline is 3. The description adds a little beyond that, clarifying that the agent's own leverage/points/fee inputs are applied uniformly to every lender and that state acts as a filter with a 'to check' fallback, but it does not explain any individual input.

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: it prices one flip at every listed lender's advertised fix-and-flip start rate and ranks results by profit. The scope (multi-lender comparison vs. a single scenario) implicitly separates it from calculate_flip_profit, but no sibling is named explicitly. An agent can still tell what it does without opening the schema.

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 implies the situation (you have one flip's numbers and want to see which lender is cheapest) and explains the effect of the optional state filter, including the nuance that non-listing lenders are kept as 'those to check'. It never states when to prefer calculate_flip_profit, get_lender_terms, or find_lenders instead, so routing between siblings is left to inference.

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