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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds material facts beyond them: public unauthenticated access and a 60 requests/min per-IP rate limit. It also restates zero state mutation, which is redundant with the annotations but harmless.

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?

It is front-loaded with the useful purpose sentence, but the middle section wastes space on a self-referential usage sentence and irrelevant alternative tools. The trailing 'Returns: Structured JSON object containing status, matched records or computed metrics, and canonical action URLs' is generic template text that adds little.

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 two-parameter read-only query this covers what matters: what is computed, the tax-year window, access and rate limits, and the shape of the result. No output schema exists, yet the return description is only a generic template rather than naming the actual summary fields, a small remaining gap.

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 explains both parameters including the tax_year starting-year convention. The description only echoes required/optional status and adds no syntax or edge-case detail, which is the expected baseline when the schema does the heavy lifting.

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 first sentence states a specific verb (Calculate), resource (SARS travel allowance tax pack totals for a vehicle), and scope (South African tax year 1 March – 28/29 Feb), and lists the returned metrics. It implicitly distinguishes the vehicle-level calculation from calculate_fleet_sars_roi, though that contrast is never spelled out.

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 a 'When to use' line and a 'Do NOT use' line naming alternatives, but the when-to-use clause is circular boilerplate ('when you specifically need to execute get_sars_summary') and the exclusions point to unrelated tools (get_fuel_prices, get_product_catalog) rather than the genuinely confusable sibling calculate_fleet_sars_roi.

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