calculate_us_fica

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

With no annotations, the description must disclose behavioral details. It lists return fields and states 'employee share', but lacks critical assumptions (e.g., wage base limit, additional Medicare tax thresholds, rounding, 2026 applicability). Partial transparency.

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?

Two concise front-loaded sentences. No superfluous words. Efficiently conveys purpose and directs to related tools.

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 simple tax calculation with one parameter and output schema, the description covers purpose and output fields. However, it omits important context (e.g., assumptions, edge cases, 2026 rate validity), making it only moderately complete.

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% with clear description. The tool's description adds no additional meaning beyond 'employee share', which is already implied. Baseline 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?

Clearly states it calculates US FICA taxes (Social Security + Medicare) for the employee share for 2026, specifying the verb, resource, and scope. The year and 'employee share' detail differentiate it from other US tax tools.

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 implies usage for FICA tax calculation but only vaguely points to list_bundles for related calculators. It does not explicitly state when to use this vs alternatives like calculate_us_federal_tax.

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