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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the description correctly focuses on conversion assumptions: default 40 hours/week, 52 weeks/year, 2,080 total hours, and the pay-period breakdown. It discloses gross-pay-only scope and points to the net-pay alternative.

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 tightly written sentences with no filler. The core conversion and output periods are front-loaded, followed by defaults and the gross-vs-net distinction.

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 small deterministic calculator with full schema coverage and a clear safety annotation profile, the description covers the conversion outputs, default assumptions, and gross-pay limitation. No output schema exists, and the description adequately lists the returned pay periods.

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%, so the schema already documents annual_salary, hours_per_week, and weeks_per_year including defaults. The description reinforces the default hours/weeks and total 2,080 hours, but adds little beyond what the schema already provides.

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?

States a specific verb and resource: converts an annual salary to an hourly rate and multiple gross pay periods. It also explicitly distinguishes the output from net pay by naming calculate_take_home_pay, making its scope clear relative to a key sibling.

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?

Explicitly says 'Gross pay only; use calculate_take_home_pay for net,' which gives a clear condition for choosing an alternative. It does not explicitly mention hourly_to_salary, the inverse tool, but the purpose makes the direction obvious.

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