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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful context by stating each item carries its official source, which tells the agent results are citable. It does not disclose whether the card is a static snapshot, how often it refreshes, or what the response shape is.

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 front-loaded sentence that leads with the resource name and then itemizes contents. The enumeration is long but each term is a distinct data domain an agent would need to match against a query, so it earns its place. Mild redundancy with the title's phrasing of 'rates and dates'.

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, the description must carry the burden of describing return values, and it does so only by listing subject areas rather than structure. For a zero-parameter aggregation endpoint, an agent still lacks guidance on whether this returns one bundled document or a set of sections, and how it relates to the more granular sibling tools.

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?

The tool takes zero parameters, so the baseline is 4. Nothing about parameter semantics needs explaining, and the description does not waste words on nonexistent inputs.

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 names a specific resource (THRIVE's Fleet Rate Card) and enumerates exactly what it contains: advisory fuel rates, BiK, mileage allowance, eVED, ZEV mandate, van grant, van benefit, plus change dates. An agent knows precisely what data comes back. It stops short of 5 because it does not differentiate itself from overlapping siblings such as get_hmrc_fleet_rates or get_company_car_tax_rates, which plausibly cover subsets of the same content.

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 statement of when to use this tool versus the many sibling rate/tax tools, and no alternatives are named or excluded. The agent must infer that this is a consolidated overview rather than a targeted lookup. Only the implicit framing ('the rates and dates UK fleets work to') hints at usage.

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