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

The description discloses advanced behavioral traits beyond the annotations, specifically detailing the calculation of maximum 2026 employee/employer contributions and its ability to evaluate specific IRS concepts like Sec. 199A QBI and Backdoor Roth effects. This adds crucial technical depth.

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 description is a dense single sentence, but it is perfectly structured to pack maximum value. Every phrase serves to define the scope, the calculations, or the advanced tax concepts addressed, leaving zero unnecessary words.

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?

Given the high complexity of the tool—which manages multiple entity types, specific IRS caps for 2026, and advanced tax strategies—the definition is extremely complete. It addresses the high-level logic that an agent would need to understand the tool's utility.

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?

Although the schema coverage is 100%, the description adds vital semantic meaning by specifying how the 'comp' and 'entity' parameters interact within the calculation. It clarifies that 'comp' can represent either W-2 wages or Schedule C net profit, which adds necessary context for the agent.

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 is highly specific, clearly defining the action (compare Solo 401k vs SEP IRA), the target audience (self-employed, LLC owners), and the primary calculative outputs. It distinguishes itself from general tax tools by focusing on optimal S-Corp W-2 salary solutions and specific contribution comparisons.

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?

It provides explicit usage guidelines by naming the persona the tool is intended for (business owners, 1099 contractors, S-Corp owners). This provides clear operational context that guides the agent to use it only when that specific user type or calculation is requested.

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