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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. 'Pure arithmetic' adds a small amount of context (no external state, deterministic), but the description says nothing about rounding behavior or the format of the resulting figure, which matters for a pay calculation.

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 short sentences, front-loaded with both conversion directions and no filler. The trailing 'Pure arithmetic.' fragment is terse and functional, though slightly clipped.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a four-parameter pure-arithmetic converter, the description plus schema plus annotations give the agent everything needed to call it correctly.

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 fully documents amount, direction, paidWeeks and hoursPerWeek, including the direction enum and defaults. The description merely restates the time-base inputs ('weekly hours and paid weeks') without adding syntax, rounding, or currency meaning beyond the schema; baseline 3 applies.

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 (convert) and resource (gross annual salary / hourly pay) and names both directions, which is enough to separate it from generic siblings like unit_convert or hours_calculator. It does not explicitly name a sibling alternative, so it falls short of a 5.

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 mention of 'your entered weekly hours and paid weeks' implies the required inputs, giving a weak cue about when the tool applies. There is no statement of when to use this versus unit_convert, hours_calculator, or time_card_calculator, and no exclusions.

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