search_botsSearch public ShareGrokBots listings by text and optional category. Returns name, credit, live bot link, and the community signal: votes from signed-in members and adds from people who opened the bot through its listing. ShareGrokBots does not test, score, or review the bots it lists. Never returns prompt text.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | ||
| category | No | (optional category) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond those hints: the meaning of votes and adds, the fact that ShareGrokBots does not test or review bots, and the explicit guarantee that prompt text is never returned. No contradiction with 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 compact and front-loaded: it opens with the purpose, then covers return fields, community signals, and critical negative constraints. Every sentence adds distinct value with no filler.
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?
With no output schema, the description does well by explaining the return payload and important caveats. However, it omits semantics for the limit parameter and does not describe pagination or result-list shape, which would make the tool fully self-explanatory.
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 only 33%, so the description must compensate. It clarifies the query parameter as text search and category as optional, but it never explains the limit parameter's meaning, default, or effect, leaving a real gap for agents.
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 uses a specific verb ('Search') with a precise resource ('public ShareGrokBots listings') and a clear scoping mechanism (text and optional category). It also lists the distinctive return fields, which differentiates it from siblings like get_bot, latest, and list_categories.
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 clearly establishes when to use the tool: when searching public listings by text or category. It does not explicitly name alternatives or state when not to use it, so it stops short of full routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct purpose: fetching one listing, listing newest, listing categories, listing most voted, and searching. No two tools appear to do the same thing, making misselection unlikely.
get_bot, list_categories, and search_bots follow a clear verb_noun pattern, but latest and most_voted are descriptive fragments without a verb. This breaks the consistency enough to be noticeable.
Five tools is a well-scoped set for a read-only listing and search service. Each tool covers a distinct user need without redundancy or bloat.
The surface fully covers the core domain: retrieving individual listings, exploring newest and top-voted content, searching, and browsing categories. No create/update operations are needed for a public listing directory, so there are no significant gaps.