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

With readOnly, idempotent, and non-destructive annotations already covering safety, the description adds useful scope: gross pay only, default hours/weeks, and optional overtime at a multiplier. It stops short of specifying rounding or exact response structure, but the core behavior is well disclosed.

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 short, front-loaded with the conversion behavior, and every sentence carries useful information. There is no redundant or filler text.

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 calculator with complete parameter descriptions and safety annotations, the description supplies the necessary output scope—weekly, monthly, and annual gross pay—plus defaults and net-pay routing. Nothing critical is missing for correct invocation.

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 description coverage is 100%, so the schema already documents all five parameters. The description repeats key defaults but does not add meaning beyond the schema, such as how overtime hours interact with annualization.

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 states a specific verb and resource: it converts an hourly wage into weekly, monthly, and annual gross pay. It also makes the direction clear against siblings such as salary_to_hourly and distinguishes gross pay from net-pay 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?

It gives an explicit alternative for net pay: use calculate_take_home_pay. However, it does not mention salary_to_hourly for the inverse conversion or clarify when other siblings like compare_states_take_home might be relevant.

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