Decide a pending screener conversation for first-time senders: allow future emails, block the sender, or mark as cold outreach.
Decide a pending screener conversation (first-time sender). 'allow' lets future emails through, 'reject' blocks, 'cold' marks as cold outreach.
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | No | Send16 API key (overrides SEND16_API_KEY env var) | |
| convoId | Yes | Conversation ID | |
| decision | Yes | Screener decision |
Changes observed during successful MCP inspections.
v0.5.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description must disclose all behavioral traits. It describes the immediate effects of each decision (allow, reject, cold) but does not explain if decisions are reversible, whether they trigger side effects, or what happens to future messages. This is a moderate gap.
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, well-structured sentence that immediately conveys the action and resource. It prioritizes key information and avoids redundancy. Every word earns its place.
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?
The description covers the core functionality and decision options. However, it lacks information about the return value or any confirmation message, and does not mention prerequisites (e.g., the conversation must be pending and from a first-time sender). For a simple tool, it is nearly complete.
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 description coverage is 100%, and the tool description adds value by elaborating on the 'decision' enum: it explains what 'allow', 'reject', and 'cold' mean in the context of future email handling. This goes beyond the schema's 'Screener decision' description.
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 action ('Decide') and the resource ('pending screener conversation'), and explains the three possible decision outcomes. It distinguishes itself from sibling tools like list_convos or add_convo_note by specifying it's for screener decisions on first-time senders.
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 indicates when to use: for pending screener conversations from first-time senders. It does not explicitly state when not to use or provide alternatives, but the sibling set includes no other screener decision tool, making the guidance adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.