salary_convert

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

With no annotations, the description must fully disclose behavior. It mentions 'purchasing power comparison,' which adds value beyond simple conversion. However, it lacks details on rate limits, authentication, or side effects. The behavioral disclosure is adequate but not comprehensive.

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 front-loaded with a clear purpose sentence, followed by a parameter list. While the parameter list is verbose, it is structured and useful. No wasted sentences, but could be more compact.

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?

The tool has 5 parameters and an output schema. The description explains the conversion and purchasing power comparison, but does not clarify how the comparison works (e.g., based on PPP indices) or describe the output format. Adequate but leaves some gaps.

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 coverage is 0%, so the description must compensate. It lists parameters with brief defaults but essentially restates schema titles (e.g., 'Salary amount', 'Source currency code'). It adds minimal extra meaning beyond the schema, but the defaults are helpful. Score 3 reflects baseline compensation.

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's purpose: 'Convert salary between currencies with purchasing power comparison.' This distinguishes it from sibling tools like convert_currency (simple currency conversion) and salary_breakdown (breaking down salary components).

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 guidance is provided on when to use this tool versus alternatives (e.g., convert_currency, salary_breakdown). There is no mention of context or exclusions, leaving the agent to infer usage from the description alone.

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