calculate_hourly_cost

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

No annotations provided, so description must carry behavioral information. It states inputs and return value but contains a mismatch: description mentions 'monthly salary' while schema uses 'annual_gross'. This could confuse agents about required input format. Overall, it gives basic behavioral traits but with inaccuracies.

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?

Three sentences cover purpose, usage, inputs, and a referral to bundle. Concise and front-loaded with purpose. However, the inaccurate input description reduces its effectiveness.

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 calculator with 3 parameters and no output schema details, description provides high-level purpose and usage. But it omits explanation of defaults (e.g., charges_pct default 45), calculation formula, and output format. The parameter mismatch further detracts from completeness.

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?

Description says inputs are 'monthly salary, social charges %, billable hours/month', but schema fields are 'annual_gross', 'charges_pct', and 'work_days' (annual). The description uses incorrect units and labels, which contradicts the schema. This misleads agents about parameter semantics.

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 computes 'fully-loaded hourly cost-to-company' and specifies use cases ('project pricing or freelance rate'). It distinguishes itself from many sibling calculators by targeting a specific cost metric.

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?

Provides explicit use cases ('project pricing or freelance rate') and directs users to related tools via list_bundles. However, it lacks explicit when-not-to-use guidance or alternative tool names beyond the bundle reference.

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