calculate_eosg

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the calculation formulas for each country and notes that contract type is identical under UAE law and end reason affects Saudi entitlement. However, it does not mention response format, rounding behavior, or handling of invalid inputs.

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 paragraph with key information front-loaded. It includes formulas and examples efficiently. Slightly verbose but generally well-structured.

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?

No output schema is provided, so the description should explain the return value. It does not specify what the output looks like (e.g., a number with currency). Also lacks details on edge cases or fractional calculations, which are likely relevant for such a tool.

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 100%, so baseline is 3. The description adds value by explaining the formulas, providing example queries, and clarifying that contract_type has identical effect for UAE and that end_reason affects Saudi entitlement. This goes beyond the schema's parameter descriptions.

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 calculates End of Service Gratuity for UAE or Saudi Arabia, which distinguishes it from sibling calculator tools. It provides specific verbs ('Calculate') and resources (EOSG for two jurisdictions), making the purpose unambiguous.

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 includes example queries and references to specific laws, giving clear context for when to use the tool. However, it does not explicitly state when not to use it or list alternative tools for related calculations.

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