Confirm the AfterLaunch key works before any growth or marketing work: which product run it is bound to, its scopes, tier and trial_ends_at, plus onboarding (feed_ready is false while the Growth Snapshot deep scan is still building, so wait before reading the Feed) and credits once metering is live. Call this first.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations provide readOnlyHint and destructiveHint, but the description adds behavior not visible in annotations: the feed_ready state and the fact that credits appear 'once metering is live'. It also reveals that the deep scan is still building during onboarding. 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 a single sentence that front-loads the purpose ('Confirm the AfterLaunch key works') and then packs useful details. It is somewhat dense but every clause adds value; not overly verbose.
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 there is no output schema, the description itself enumerates the key return fields and explains the onboarding state and credit timing. This covers the essentials for an agent to understand what to expect, making it complete for a first-call health check 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 input schema is empty ({}), so there are no parameters to explain. The description correctly focuses on the tool's output rather than inputs. Baseline of 4 applies for zero parameters.
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's function: 'Confirm the AfterLaunch key works before any growth or marketing work' and enumerates the specific data returned (product run, scopes, tier, trial_ends_at, feed_ready, credits). This differentiates it from sibling tools like list_feed or get_activity.
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 explicitly instructs 'Call this first' and provides a conditional for using the Feed: 'wait before reading the Feed' until feed_ready is true. This gives clear ordering relative to other tools, even if no alternative tool is named.
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.
Most tools have clearly distinct purposes, and descriptions are thorough. A few pairs (e.g., ship_move vs set_output_status, dismiss_gap vs skip_move) overlap on the dismissal concept but operate on different surfaces, so an agent can usually tell them apart with careful reading.
All tool names follow the same snake_case verb_noun pattern (e.g., get_move, create_checkout, untrack_prompt). Retrieval tools consistently use get_ for single items and list_ for collections, and action verbs are precise, so the naming is fully predictable.
42 tools is heavy by any standard, exceeding the 25+ threshold in the calibration. While each tool may earn its place given the breadth of the domain, the sheer number will overwhelm an agent and complicate tool selection.
The tool set covers the main lifecycles well: moves (list/get/ship/skip/archive/undo/update), outputs (list/get/ship/redraft), connections (list/start/poll/disconnect), prompts (track/untrack/list), and scans (refresh/get/set intensity). Minor gaps exist, such as no direct edit for KB pages, but record_insight partially fills that.