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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful context about the included tax categories and the specific assumption of a 65-year-old single filer on $40,000 of withdrawals, but it does not disclose the output format or behavior for invalid input. This is adequate given 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?

The description is compact and dense: two sentences cover content, scope, the estimation scenario, and input instructions. Every clause earns its place, and the main subject is front-loaded.

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?

For a read-only informational tool with one optional parameter and no output schema, the description is complete. It tells an agent what tax topics are covered, the specific estimate scenario, the geographic scope, and how to request one state or all states. No required information for correct invocation is missing.

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 coverage is 100%; the single optional 'state' parameter is already documented as a state name or abbreviation, and the description repeats this guidance without adding meaning beyond the schema. The baseline of 3 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 clearly defines the tool's purpose: explaining how a US state taxes retirement income, with specific coverage of Social Security, pensions, IRA/401(k) withdrawals, estate/inheritance tax, sales and property tax, and an effective income tax estimate. It also states the scope (all 50 states and DC), which distinguishes it from sibling tools like federal_tax_estimate.

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 gives clear input guidance: provide a state name or abbreviation, or omit it for every state. It does not explicitly name alternatives or provide when-not-to-use conditions, but the context of state-specific retirement taxation is clear enough for an agent to know when this tool is relevant.

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