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

The term 'search' implies a read-only operation, but the description does not explicitly state that it has no side effects or that it returns a list of results. With no annotations to clarify, the description partially carries the burden but could be more explicit.

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?

The description is a single, concise sentence with no superfluous words. It is well-structured and easy to parse.

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?

While the tool is simple, the description omits essential details about parameters and result behavior. Without an output schema, an agent would need to infer how to construct a valid query and interpret the response. The lack of parameter explanations makes it incomplete for reliable invocation.

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 schema has two parameters (query, limit) with zero description coverage. The description does not explain what 'query' means (e.g., search terms, filters) or how 'limit' behaves (e.g., maximum results). It fails to compensate for the lack of schema documentation.

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 clear resource ('BOE item titles and text'), which distinguishes it from sibling tools like boe_day and tenders_search.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., boe_day for daily records, tenders_search for tenders). The description only states what it does, not when it should be preferred.

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