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

Annotations already establish readOnly, idempotent, non-destructive, closed-world semantics, so the safety profile is covered. The description usefully discloses that it emits a set of derived figures (gross monthly, annual, biweekly, weekly, hourly), but says nothing about rounding, assumptions, or the default-hours behavior beyond what the schema states.

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?

One compact sentence with the input frequencies front-loaded before the output list; no filler. It could be marginally tighter but every clause earns its place.

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 stateless calculator with annotations carrying the safety profile and no output schema needed, the description covers what the tool accepts and returns. Only the absence of usage routing against sibling calculators leaves a small gap.

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 67% and the schema already documents amount, frequency, and hours_per_week (with default 40). The description's spelling out of frequency labels ('every two weeks', 'twice a month') adds modest mapping value but no syntax or constraint detail beyond the schema.

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 ('Converts') and resource (pay amount) and enumerates both the accepted frequencies and the produced outputs, so the transformation is unambiguous. It doesn't distinguish itself from calculator siblings like rent_to_income or prorated_rent, but the core purpose is clear.

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 indication of when to use this versus the other income tools (how_to_verify_income, start_income_verification, rent_to_income, etc.), nor any prerequisites or exclusions. Usage must be inferred entirely from the name.

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