salary_calculator

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

The description does not disclose behavioral traits such as the use of default values for hours_per_week (40) and days_per_week (5) or how biweekly is handled (present in enum but not mentioned). With no annotations, the description fails to provide sufficient transparency about conversion assumptions.

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 a single sentence that is concise, front-loaded, and contains no redundant information. It effectively communicates the core purpose.

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?

Given no output schema, the description should explain what the tool returns (e.g., converted amounts for all periods?). It also omits details about default assumptions and the handling of biweekly. This lack of completeness could confuse an AI agent about the tool's exact output.

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 baseline is 3. The description adds no additional meaning beyond the schema—it does not explain how parameters like hours_per_week affect conversion or the significance of from_period.

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 clearly states the tool converts between hourly, daily, weekly, monthly, and annual salary figures. The verb 'convert' and resource 'salary figures' are specific and distinguish it from sibling calculators like age_calculator or bmi_calculator.

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 explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for salary conversion but lacks when-not or alternative recommendations. With many sibling calculators, the agent must rely on the tool name and description to disambiguate.

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