Topics RISING on the wire this window vs the previous one — velocity over a controlled vocabulary, counting distinct events (syndicated copies collapse). Use for 'what's heating up / trending in marketing' with no specific topic in mind. Args: window_days (default 7, capped at 90).
| Name | Required | Description | Default |
|---|---|---|---|
| window_days | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the full burden. It discloses key behaviors: controlled vocabulary, distinct event counting, and window_days cap. However, it does not explicitly confirm read-only status or mention rate limits.
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?
Two sentences with no wasted words. First sentence defines the output; second sentence gives usage context and parameter details. Well-structured and front-loaded.
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?
For a simple tool with one optional parameter and no output schema, the description covers purpose, usage, and parameter semantics. It lacks explicit return format or pagination, but the overall context is sufficient for an agent.
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 0%, but the description adds full semantics for window_days: default 7, capped at 90. This compensates completely, providing value beyond the schema.
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 lists trending topics on the wire, with specifics about velocity measurement and distinct event counting. It distinguishes from siblings by usage context: 'Use for what's heating up / trending in marketing with no specific topic in mind'.
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 states when to use (no specific topic) and implies when not (specific topics, which are covered by siblings like earlywire_search). Could be more explicit about alternatives, but sufficient guidance is provided.
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 uniquely identifiable purpose: coverage checks answering capability, get_item retrieves a single item, search handles queries, topic_pulse explores discussion around a topic, trending shows rising topics, and whats_new provides the freshest items. No ambiguity between them.
All tools follow a consistent 'earlywire_' prefix and use descriptive, lowercase snake_case names (coverage, get_item, search, topic_pulse, trending, whats_new). The naming pattern is uniform and predictable.
With 6 tools, the server is well-scoped for a marketing/growth intelligence niche. It provides essential operations without being too sparse or overloaded. Each tool contributes to a coherent workflow.
The tool surface covers the full lifecycle of interacting with the curated intelligence: discovery (trending, whats_new), search (search), deep dive (get_item, topic_pulse), and scope checking (coverage). No obvious gaps for a read-only intelligence service.
