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 new behavior: a hard cap of 15 results, newest-first ordering, and the fields returned (date, summary, URL). It does not say what happens on zero matches, which keeps it below a 5.

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?

Two sentences, zero waste, and the most decision-relevant fact (what it searches) is front-loaded before the result-shape detail. Nothing could be removed without losing 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?

For a one-parameter read-only search tool, the description plus annotations plus full schema coverage covers everything needed to call it correctly, and it compensates for the absent output schema by naming the returned fields. Only the empty-result behavior is unstated.

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% and the single query parameter already carries example values ('salary sacrifice', 'ZEV mandate', 'Transit'). The description only restates 'by keyword', adding no syntax, matching, or multi-term guidance beyond the schema.

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 (search) plus resource (THRIVE's UK fleet news and analysis) plus the retrieval mode (by keyword). This is clearly distinguishable from the sibling data getters such as get_uk_fuel_prices or get_fleet_rate_card, which return metrics rather than news stories.

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?

Usage is implied by 'search ... by keyword' — an agent can infer it should call this when it needs news/commentary rather than numeric fleet data. However, no explicit when-to-use condition, no exclusions, and no named alternative (e.g. get_guide) are given, so the routing decision is left partly to inference.

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