Search Cello's documentation to find relevant articles, guides, code examples, and API references. Use this when you need to answer a question about Cello, figure out how to integrate Cello, or track down specific implementation details.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds useful context about the types of documentation content searched, but it does not describe the return format, pagination, or any limitations. With annotations covering safety, this is acceptable but not rich.
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 two sentences with no fluff. The first sentence states the action and resource, the second gives concrete usage scenarios. Every word earns its place.
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 simple one-parameter tool with solid annotations, the description covers what it does, what content it searches, and when to use it. It does not detail the exact response structure, but the description is adequate for a documentation search tool.
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 covers the only parameter (query) with a description "Search query," so coverage is 100%. The description does not add any extra meaning to the parameter beyond what the schema already provides. Baseline 3 applies.
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") and resource ("Cello's documentation") and lists the types of content (articles, guides, code examples, API references). This clearly distinguishes it from sibling tools that retrieve events, metrics, or referrers.
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 description gives explicit use cases: "answer a question about Cello," "figure out how to integrate Cello," and "track down specific implementation details." However, it does not mention when not to use this tool or name any alternatives, so it stops short of full 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 targets a distinct aspect of the Cello platform: events, integration status, metrics, recommendations, referrers (general and top), and documentation search. No two tools have overlapping purposes; descriptions clearly differentiate them.
All tools follow a consistent pattern with 'cello' prefix, verb (get or search), and snake_case noun. The verb choice is appropriate for each operation, and the naming is predictable and uniform.
With 7 tools, the set is well-scoped for a referral program analytics and diagnostics server. Each tool fills a necessary role without being excessive or too sparse.
The tool set covers all key read-only diagnostics: events, integration health, metrics, recommendations, referrers, and documentation. However, it lacks any write or configuration tools, which may be expected for a comprehensive integration server, but the surface is complete for its apparent diagnostic purpose.