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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered; the description adds that this is an estimate/simulation spanning specific statutory lines (1a-38, 6b, 13a, 13b) and ceilings. It does not explicitly say results are non-authoritative planning estimates or discuss assumptions baked into defaults, which would have been valuable added context beyond the annotations.

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 front-loaded with the trigger phrase, but the whole definition is one ~100-word run-on sentence with a dense comma/"or" list that is harder to scan than a short lead sentence plus bullets. Every clause is substantive, but structure costs it.

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 8 parameters and no output schema, the description does the necessary work of naming what comes back (return lines, bracket room, 0% LTCG room, ACA cliff status, 8962/8995/Schedule 1-A flow-through). What is missing is an indication of whether results are single-year only and what the numeric output shape roughly is, though the absence of an output schema is partly offset by the conceptual enumeration.

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 every parameter maps to an explicit Form 1040 line, so the schema already carries the semantics. The description adds no per-parameter meaning (e.g., how netLtcg interacts with the 0% ceiling or whether rothConversions are included in bracket room), so the baseline of 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+resource set (simulate a full Form 1040 estimate, remaining bracket room, 0% LTCG headroom, ACA cliff, SS/QBI/OBBBA flow-through) and enumerates the line-level outputs, so an agent can immediately tell what it produces. It is clearly differentiated from siblings like calculate_rmd_and_tax_cliffs because it is the only holistic full-return simulation.

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?

"Use this tool whenever a user asks for..." followed by five concrete trigger scenarios is unusually strong when-to-use guidance. It stops short of naming when NOT to use it or pointing to alternatives, even though bracket-room and Roth-conversion overlaps with calculate_rmd_and_tax_cliffs and calculate_roth_conversion are obvious candidates for a routing note.

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