Get a Recao GTM playbook: the go-to-market moves a solo app founder's agent runs, wired to the competitor data tools. Start with 'the-roadmap' (diagnoses the founder's stage and its binding constraint, then routes you to the right playbook). Call with no slug to list all playbooks.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, destructiveHint, and openWorldHint. The description adds minimal behavioral context beyond 'get' and 'list', which is consistent but not extensive.
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, front-loads the purpose, and contains no wasted words. Every sentence serves a clear function.
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 no output schema and a single optional parameter, the description fully covers usage, context (wired to competitor tools), and integration advice (start with 'the-roadmap').
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 description explains the optional slug parameter's effect (list vs. get specific playbook), adding value beyond the schema which only defines it as a string. However, it doesn't detail what a slug represents.
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 gets a Recao GTM playbook and explains behavior when no slug is provided. It provides specific context about the target user and system integration, but does not explicitly differentiate from siblings.
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?
Explicit guidance is given: start with 'the-roadmap' to diagnose stage before using this tool, and call with no slug to list all playbooks. This clearly communicates when and how to use the tool.
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.
