Get today's content for all subscribed channels. Call this once per day.
Returns styled HTML (drop into your email where {4bots} goes) and plain text.
Check low_balance — if true, send your human to manage_url to top up.
| Name | Required | Description | Default |
|---|---|---|---|
| session_token | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully carries the burden of behavioral disclosure. It reveals that the tool returns both styled HTML and plain text, and importantly flags the low_balance field and the action to take if it is true. This adds valuable context beyond what the schema or annotations would provide, though it does not mention error handling or side effects.
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 extremely concise: three sentences, front-loaded with the purpose, and every sentence adds value (usage frequency, return format, and a behavioral note). No wasted 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?
Given the tool's simplicity (one parameter, no output schema), the description covers the main purpose, usage frequency, return types, and a key behavioral trait (low_balance). It lacks parameter description, but the session_token is somewhat self-explanatory. Overall, it is fairly complete for a simple tool, though a note on error conditions would round it out.
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 coverage is 0% (no parameter descriptions in the schema), so the description must compensate. However, the description does not mention the required session_token parameter at all, failing to explain its purpose or format. This is a significant gap for a single required parameter.
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 'today's content for all subscribed channels', combining a specific verb and resource. It distinguishes itself from siblings like get_summary, get_template, and list_channels by focusing on the daily bundle of content for all subscribed channels.
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 explicitly says 'Call this once per day', providing a clear usage frequency guideline. While it does not explicitly exclude other tools or state when not to use it, the daily frequency is a strong contextual hint that helps the agent decide when to invoke this tool over alternatives.
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.
Each tool has a clearly distinct purpose: creating a setup link vs. starting a subscription, previewing sample content vs. fetching the daily bundle, listing channels vs. voting, etc. Descriptions explicitly clarify differences (e.g., 'For a fast start without human input, use start_subscription').
All tool names follow a consistent verb_noun pattern using snake_case: create_setup_link, get_bundle, get_session, get_summary, get_template, list_channels, start_subscription, try_sample, vote. No mixed conventions or vague verbs.
9 tools is well-scoped for a content subscription service. Each tool serves a single, necessary function (subscription activation, daily content, account info, channel listing, voting, etc.) with no redundancy or bloat.
The tool surface covers the full lifecycle: subscription start (two paths), daily content retrieval, account status, catalog/pricing, email template, channel discovery, and community voting. The only minor gap is no cancellation tool, but the manage_url in get_session handles that externally. No dead ends for the core workflow.