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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two genuinely useful traits beyond that: results are 'bounded' (paginated) and consist of 'metadata' rather than full article content. It stops short of stating result counts, sort order, or rate limits.

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 a single short fragment with no wasted words, but that brevity is achieved by omission rather than precision. There is no front-loaded statement of what the tool does or how to call it.

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?

An output schema exists, so return values need not be explained, but for a two-parameter search tool with 0% schema description coverage and four sibling BBC tools, the description omits the query/pagination semantics and the routing guidance an agent needs to invoke it correctly.

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 coverage is 0%, so the description must carry the burden, but it only obliquely hints at paging via 'a bounded page'. The required 'q' query parameter and the 'page' parameter's semantics, format, and defaults are never described.

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 the resource ('BBC search-result metadata') but supplies no verb and does not distinguish this tool from siblings like bbc_headlines, bbc_article, or bbc_author. It largely restates the name, leaving the agent to infer that this is a keyword search endpoint.

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 and no mention of alternatives. An agent cannot tell from this text whether bbc_search is for full-text queries, site navigation, or something else, nor when to prefer bbc_headlines or bbc_article instead.

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