search

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

With annotations already covering read-only, idempotent, and non-destructive behavior, the description adds valuable context beyond them: the exact return shape (flat list of fields) and the underlying hybrid search backend (semantic+BM25+RRF). It doesn't cover auth needs or rate limits, but those are less critical given the annotations.

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 four compact sentences with no filler. It front-loads the tool's identity and return format, then adds backend and alternative details. The opening 'OB1-compatible' is somewhat jargon-heavy, but overall it is efficient.

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 search tool with no output schema, the description usefully documents the return fields and backend. However, it omits any parameter guidance and fails to distinguish this generic search from many sibling search tools beyond search_hybrid, leaving an agent with incomplete routing information.

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 0% for the two parameters (query, limit). The description does not mention either parameter or their semantics, so it fails to compensate for the lack of schema-level documentation. The agent must infer from parameter names alone.

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 identifies the tool as an OB1-compatible search adapter that returns a flat list of {id, title, url, snippet} for connector ecosystems. It distinguishes itself from search_hybrid by output richness, but does not explain how it differs from other search siblings like search_semantic or search_text.

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?

It gives a clear usage context ('for connector ecosystems') and explicitly names the alternative for richer output ('use search_hybrid'). However, it provides no when-not guidance or distinction from other search tools in the sibling list.

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