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

Annotations already declare readOnly=true, destructive=false, closed-world, so the safety profile is covered. The description adds real behavioral value by naming the computed outputs: tax gross-up penalty, break-even borrowing rate, IRC Sec. 163(d) Form 4952 deduction, and LTV margin-call buffer. It omits assumptions (e.g. assumed capital gains rate) and any caveats, which keeps it short of a 5.

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 usage trigger is front-loaded in the opening clause, followed by a compact list of computed quantities. Dense but every clause carries information; the parenthetical cash-use examples are useful rather than 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?

With 7 fully documented parameters and no output schema, the description does the needed work by enumerating the outputs computed. It stops short of describing the comparison result format or the tax assumptions baked in, which would matter for interpreting the break-even rate.

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 every parameter is already documented in the schema, setting the baseline at 3. The description links interestDeductible to the 163(d)/Form 4952 deduction and ties marketReturn/LTV to the margin-call buffer, adding modest conceptual framing but no new per-parameter meaning.

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 comparison verb (sell appreciated stocks/ETFs vs. borrow via SBLOC/PAL/margin) with a concrete decision framing. It is unmistakable against siblings like calculate_roth_conversion or analyze_estate_tax_and_stepup, which address entirely different planning questions.

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?

Gives explicit trigger conditions: user needs cash liquidity for a real estate bridge, tax bill, tuition, or business investment, and asks whether to sell or borrow. It does not name when NOT to use it or point to an alternative tool, but no sibling overlaps this decision space, so the gap is minor.

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