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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description is not carrying the safety burden. It adds real context on top: results are restricted to active UK used-bike listings, matching covers title/brand/model, and each returned id is a listing id that can presumably be fed to fetch or get_listing_detail. It stops short of noting result limits, pagination, or ordering.

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?

Four short sentences, front-loaded with the compatibility purpose and then the actual behavior. No filler, though the return-shape sentence partly duplicates the output schema and could have been trimmed.

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, and safety is covered by annotations. The remaining gap is routing: with ~30 siblings including search_bikes, search_by_location and fetch, the description gives no basis for choosing this tool, and says nothing about result caps or paging.

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 100% and there is only one parameter, so the baseline would be 3. The description earns above baseline by explaining what the query actually matches against (title, brand, model), which the schema's bare 'Free-text query' does not convey.

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 and resource: free-text search over Cyclesite's active UK used-bike listings, with the match fields (title, brand, model) named. It is clear what the tool does, but it never distinguishes itself from the sibling search_bikes, which an agent will inevitably compare it against.

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?

The opening phrase implies the intended consumer (OpenAI deep-research / company-knowledge integrations), so usage context is inferable. However, there is no explicit when-to-use versus search_bikes, no statement of when this is preferred over fetch or search_by_location, and no exclusion guidance.

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