Returns a prioritized list of best-practice recommendations for improving your referral program across three areas: Activation, Sharing, and Conversion. Use when a user asks how to improve their program, what they're missing, or what to do next after confirming integration health.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| tasks | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, which the description does not contradict. The description adds that output is organized into three areas, but does not disclose additional behavioral traits such as data source or update frequency. Given annotation coverage, the description provides moderate added context.
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 consists of a single, well-structured sentence that efficiently states purpose and usage context. Every word adds value with no redundancy.
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?
Given the tool's simplicity (no parameters, no nested objects, output schema exists), the description fully covers what the tool does and when to use it. The presence of an output schema reduces the need to explain return format.
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?
There are zero parameters, so schema coverage is trivially 100%. The description does not need to add parameter information. Baseline 4 is appropriate as no compensation is required.
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 clearly states the tool returns a prioritized list of best-practice recommendations for improving referral programs, specifically across Activation, Sharing, and Conversion. It differentiates from sibling tools by focusing on improvement advice rather than data retrieval.
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 explicitly states when to use: when a user asks how to improve their program, what's missing, or what to do next after confirming integration health. It provides clear context but does not explicitly mention alternatives or when not to use.
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.