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

No annotations are provided, so the description carries the full burden. It does disclose the computed outputs (total km, business km, business %, fuel expenditure) and the period boundary, implying a read-only aggregation, but it never states that it is non-mutating, what happens when underlying trip/fuel data is missing or partial, or whether the result is persisted.

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?

A single dense sentence with the verb and resource front-loaded and no filler. It is long but every clause (tax year window, returned metrics) contributes information.

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?

With no output schema and no annotations, the description does list the key return fields, which is helpful. However, for a computation tool that depends on other entities (trips, fuel logs), it omits data-precondition behavior and error/empty-state handling, leaving real 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 description coverage is 100%, so the schema already documents both parameters. The description adds the SARS year convention (1 March start, 28/29 February end), which marginally enriches tax_year semantics but does not explain formatting, defaults, or how an omitted tax_year is resolved.

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?

States a specific verb (Calculate) and a precise resource (official SARS travel allowance tax pack totals for a single vehicle over the SA tax year), and enumerates the returned aggregates. Scope (single vehicle, per tax year) implicitly separates it from calculate_fleet_sars_roi and get_sars_compliance_guide, though no sibling is named explicitly.

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 tax-year window (1 March to 28/29 February) gives useful framing, but there is no explicit statement of when to use this versus calculate_fleet_sars_roi, get_sars_compliance_guide, or list_sars_trips. Prerequisites (e.g. whether trips and fuel logs must already be captured) are left to inference.

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