calculate_belgian_salary

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

With no annotations, the description must disclose behavioral traits. It mentions 'approximation' but does not describe limitations, assumptions (e.g., tax year, marital status), error conditions, or authentication needs. The agent lacks information on when results may be inaccurate.

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 brief with two sentences: first defines purpose, second lists return fields and a helpful cross-reference. Every sentence adds value with no redundancy.

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 is simple with one parameter and an output schema (implied). The description lists key return fields and notes approximation. The pointer to list_bundles provides context for related tools. It is nearly complete but could mention input constraints (e.g., valid salary range) or precision details.

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% for the single parameter, so baseline is 3. The description adds no new semantic meaning beyond 'Gross monthly salary in euros' already in 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?

The description clearly states 'Convert Belgian gross monthly salary to net salary (approximation)', providing a specific verb and resource. It distinguishes from numerous sibling calculators by specifying 'Belgian' and pointing to related 'finance-belgique' calculators via list_bundles.

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?

The description indicates its purpose but lacks explicit guidance on when to use versus alternatives like calculate_belgian_income_tax or calculate_belgian_social_contributions. It only mentions list_bundles for related tools, which is a pointer but not a clear directive.

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