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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that: it never says what the calculation returns, whether it is deterministic against a fixed statutory year, or which tax-year parameters it assumes. For a planning calculator with no output schema, that leaves the agent guessing at the response shape.

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?

It is a single sentence, front-loaded with the trigger phrase and packed with the four qualifying scenarios, with no filler or repetition. The density makes it slightly harder to scan than a short bulleted trigger list would be, but nothing is wasted.

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?

Seven parameters, two of them required, are fully documented in the schema, so input completeness is fine. The gap is on the output side: with no output schema, the description should say what comes back (tax cost, bracket headroom, IRMAA surcharge, pro-rata taxable fraction) and it does not. For a multi-scenario financial calculator, that is a meaningful omission.

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%, and the schema itself explains IRA basis, Form 8606 provenance, the IRMAA lookback at 63+, and the OBBBA Senior Deduction at 65+. The description adds no further parameter meaning, so the baseline 3 for a fully documented schema is appropriate.

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 names a concrete verb-and-resource pairing (convert Traditional/Rollover IRA to Roth and calculate the tax cost) plus three specific modeling capabilities: bracket/IRMAA cliff ceilings, the Sec. 408(d)(2) pro-rata rule, and the Mega Backdoor 401(k). That is far more specific than a title restatement. It does not, however, contrast itself with siblings like calculate_rmd_and_tax_cliffs or simulate_form_1040_and_bracket_room, which overlap on the bracket-room modeling.

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 phrase 'Use this tool whenever a user asks...' enumerates four concrete trigger scenarios (conversion sizing, cliff avoidance, backdoor pro-rata, mega backdoor), which gives an agent a clear entry condition. There is no explicit when-not guidance or named alternative for adjacent questions like RMD cliffs or straight 1040 simulation.

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