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

With no annotations, the description carries the entire behavioral burden. It discloses only the cost ('1 credit'), which is genuinely useful, but says nothing about result format, ordering/relevance, truncation behavior, or permissions, leaving the agent to discover these empirically.

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 compact clauses, front-loaded with the purpose and the action; the cost note is separated in parentheses. There is no wasted wording, though one more sentence of routing guidance would have been a better use of space than nothing.

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 search tool with full schema coverage and no output schema, the definition is minimally adequate. It omits result shape and ranking behavior, which an agent calling a search endpoint would reasonably want to know.

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 both the query and limit parameters (with its 1-50 range) are documented structurally. The description adds no syntax or query-language guidance beyond the schema, so baseline 3 applies.

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') and a named resource scope ('GOV.UK guidance, news and publications'), which lets an agent distinguish it from legislation_search and petitions_search. However, it never explicitly contrasts with the closest sibling govuk_page (fetching a known page), so the differentiation is inferred rather than stated.

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 when-to-use guidance, no exclusions, and no named alternative. An agent must guess that govuk_page is for retrieving a known page and this tool for discovery, and nothing addresses edge cases such as when to prefer legislation_search for statutory material.

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