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

With no annotations, the description carries the full behavioral burden. It does disclose that missing inputs fall back to documented defaults and lists the computed outputs, but it does not explain how results are returned, what assumptions or formulas are used, or whether the tool is a pure computation with no side effects.

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 with no wasted words beyond the duplicated 'calculator' typo. The key outputs are front-loaded and the default behavior is mentioned, making it efficient despite minor grammatical awkwardness.

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 simple calculator with all-optional parameters that are fully documented in the schema, the description covers the outputs and default behavior. However, since there is no output schema and no annotations, the response shape and the relationship between inputs and outputs are left unstated, requiring inference.

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%, with all five parameters having names, descriptions, defaults, and ranges. The description adds only generic default-fallback context, which aligns with the schema, so it does not need to repeat individual 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 says to run the annual leave loading calculator and enumerates the outputs: base weekly pay, base pay for the leave period, leave loading, and penalties. This makes the operation and resource clear, though the wording is awkward ('calculator calculator') and it does not explicitly differentiate itself from siblings like calculator_describe.

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?

There is no guidance on when to use this tool versus alternatives such as calculator_describe or submit_enquiry. The only usage-related information is about default fallback, which is behavioral rather than selection guidance.

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