us_income_tax_estimate

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description is not expected to re-state safety. It adds useful context by specifying the tax year (2024) and that it applies to individuals, but it does not describe the output format or calculation assumptions.

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 two short sentences, front-loaded with the core action. Every word contributes to understanding the tool's scope.

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 no output schema, the description should mention what the tool returns, but it does not. It also lacks details on whether the estimate includes standard deductions or credits. However, the tool is simple and the purpose is clear, so it's not completely inadequate.

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?

Both parameters are fully described in the input schema (taxable_income and filing_status with allowed values). The description adds no additional parameter semantics; it merely lists filing statuses in the prose, which duplicates the schema.

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 states 'Estimate 2024 US federal income tax (individuals)' with a specific verb ('estimate') and resource ('2024 US federal income tax'), and lists filing statuses. It distinguishes from sibling self_employment_tax by specifying 'individuals' and the type of tax.

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?

No guidance is provided on when to use this tool versus alternatives like self_employment_tax or other financial calculations. The description only mentions filing statuses, which are parameters, not usage scenarios.

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