Replace a pending growth move's marketing draft body before shipping. A draft carrying an unfilled placeholder or a broken link is refused rather than saved. Free; requires the 'act' scope.
| Name | Required | Description | Default |
|---|---|---|---|
| move_id | Yes | Move id (uuid), from list_feed. | |
| draft_content | Yes | The replacement draft body, 1 to 20000 characters. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses auth requirements ('requires the ''act'' scope'), cost ('Free'), and validation behavior ('refused rather than saved'). These go beyond the annotations, which only indicate non-read-only and non-destructive.
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?
Three sentences, each carrying distinct information: purpose, validation behavior, and cost/scope. No redundant words.
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?
With simple parameter set and annotations, the description covers the core operation, constraints, and preconditions. It doesn't specify return value, but that's a minor gap for an update operation.
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?
Schema covers both parameters with descriptions (move_id from list_feed, draft_content 1-20000 chars). The description adds no extra semantic detail beyond the schema, so 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 the specific verb 'Replace' and identifies the resource as 'a pending growth move's marketing draft body before shipping,' clearly distinguishing it from sibling tools like redraft_output or ship_move.
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 provides clear temporal context ('before shipping') and implies the tool is for updating drafts of pending moves, but it doesn't explicitly name alternatives or state when not to use it.
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 follow a clear action+resource pattern (get_, list_, set_, ship_, etc.) with distinct purposes. A few boundaries could cause confusion, such as get_move vs get_output (both return drafts) and ship_move vs set_output_status (both mark things shipped), though descriptions mitigate this sufficiently.
The overwhelming majority use consistent snake_case verb_noun naming (list_feed, ship_move, get_visibility). The only outlier is 'whoami', a common convention but not verb_noun; otherwise the pattern is highly predictable.
At 41 tools, the surface is well over the 25-tool threshold for 'too many'. While the domain is broad, this volume places significant cognitive load on agents and suggests some consolidation or modularization could help.
Core workflows for moves and outputs are covered (create/list/get/update/ship/skip/undo). However, the tool descriptions reference 'approve_output' as the publishing action, yet that tool is absent from the list, leaving a dead end for channel distribution. There are also no tools for editing competitors or managing Memory pages beyond recording insights.