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

No annotations are provided, so the description carries the full burden. It discloses the return fields (e.g., net_biweekly) but does not mention side effects, permissions, rate limits, or assumptions about tax calculations. The description is moderately transparent but incomplete.

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 sentences with no extraneous information. It front-loads the purpose and return values, then directs to related tools. Every sentence contributes value.

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 tool's moderate complexity and the presence of an output schema (as per context), the description adequately covers the return structure and hints at related tools. It does not cover edge cases or assumptions, but the schema handles parameter constraints. Nearly complete for the typical use case.

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?

The input schema has 100% coverage, providing descriptions for all three parameters. The description adds minimal extra meaning beyond the schema, such as linking parameters to 'federal/state withholding and FICA', but does not significantly enhance understanding. 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?

The description clearly states the tool estimates 'US bi-weekly net paycheck after federal/state withholding and FICA', providing a specific verb and resource. It does not explicitly differentiate from sibling tools like calculate_us_federal_tax, but mentions related calculators via list_bundles, which is adequate.

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 provides some guidance by directing users to list_bundles for related 'finance-us' calculators, implying alternatives exist. However, it lacks explicit when-to-use or when-not-to-use criteria, prerequisites, or context compared to siblings.

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