get_referral_dashboard_guideExplain how to embed and manage the referral dashboard experience.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | ||
| title | Yes | ||
| sections | Yes | ||
| description | No |
Changes observed during successful MCP inspections.
Input schema / additionalPropertiesRemoved value: -falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It indicates the tool is informational ('Explain'), implying no mutations, but does not disclose what the explanation includes (e.g., step-by-step guide, code examples) or any limitations. This is minimally transparent but lacks behavioral depth.
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 a single, front-loaded sentence that directly and efficiently states the tool's purpose with no redundant words or unnecessary details.
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 low complexity (zero parameters, informational tool) and the presence of an output schema, the description sufficiently covers the tool's scope. It does not detail what 'embed and manage' entails, but the output schema likely provides the response structure, and the description is adequate for a guide 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 tool has zero parameters, so the baseline is 4. The description adds contextual meaning by specifying the tool covers 'embed and manage' of the referral dashboard, which is useful despite no parameter details being needed.
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 the specific verb 'Explain' with a clear resource ('the referral dashboard experience') and scope ('embed and manage'), which distinguishes it from sibling tools like explain_referral_flow or generate_referral_* snippets. It clearly states what the tool does.
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?
No guidance is provided on when to use this tool versus alternatives. The description only states the tool's function without mentioning related tools or exclusions, leaving the agent to infer usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.