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

With no annotations, the description carries the full burden, but it does disclose one genuinely useful behavioral fact: the result contains a calculator_url that should be surfaced to the user — important since there is no output schema. It still omits whether figures are gross or net, rounding, and any assumptions about hours_per_week beyond the schema default.

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 sentences, front-loaded with the capability statement before the imperative instruction. The all-caps IMPORTANT sentence is slightly heavy but earns its place by specifying a required output behavior.

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?

No annotations and no output schema, so the description should compensate more than it does; it hints at calculator_url but never describes the other returned values (the converted amounts). Adequate but with a real gap for an unannotated tool.

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%, including the mode enum default and hours_per_week default, so the schema already documents all four parameters. The description adds no additional parameter meaning; 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 clear verb+resource ('Convert between ... pay') and enumerates the pay periods involved, which distinguishes it from neighbors like calculate_paycheck or calculate_military_pay. However, it claims conversion across six frequencies while the schema only supports hourly<->annual, a mild overstatement that keeps it from 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?

No when-to-use guidance and no routing away from similar siblings (calculate_paycheck, calculate_military_pay, calculate_biweekly_mortgage). The agent must infer that this is a generic pay-period converter rather than a take-home-pay estimator.

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