digestAggregate the top-N articles across selected verticals for the requested window. Heaviest action — counts more against the per-agent rate limit. Use this for 'read me today's tech news' style prompts.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| window | No | 24h | |
| verticals | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that this is the 'Heaviest action — counts more against the per-agent rate limit', which is critical behavioral information not captured in the annotations. It also reinforces the read-only nature implied by readOnlyHint=true, with no contradictions.
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 deliver clear functionality, usage context, and rate-limit warning with zero redundancy. Every sentence serves a purpose.
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 tool with three simple parameters and no output schema, the description covers the core purpose, parameter semantics, and a behavioral note. It could optionally mention the return format but is not deficient.
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 description maps the three parameters (limit, window, verticals) to natural language ('top-N', 'requested window', 'selected verticals'), but does not explain enums or defaults. Given 0% schema coverage, the description adds moderate semantic value but lacks detail on parameter constraints.
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 a specific verb 'aggregate' and clearly identifies the resource 'top-N articles across selected verticals for the requested window', making the tool's purpose explicit. It also provides an example use case, distinguishing it from sibling tools like search_articles or get_vertical_briefing.
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 states when to use this tool ('Use this for 'read me today's tech news' style prompts') and warns about its heavy rate limit cost. While it doesn't list alternative tools for when not to use it, the guidance is clear and actionable.
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 distinct purposes, but there is overlap between `get_my_private_feed`, `subscribe_topic`, and `list_subscriptions`—all return or manage feed URLs, which could confuse an agent. Otherwise, categories like publisher, fund manager, and search tools are clearly separated.
All tools use consistent snake_case with a verb_noun pattern (e.g., `get_article`, `search_articles`, `publisher_upload_audio`). Exceptions like `digest` are single-word verbs but still fit the pattern. No mixed conventions are present.
With 37 tools, the server exceeds the 25-tool threshold considered 'too many' by the rubric. While the broad scope (news, podcasting, publishing, fund management, embedding) justifies a large surface, the count still adds cognitive load and would benefit from splitting into separate servers.
The tool set covers the major domains: search, retrieval, subscriptions, publishing, fund manager operations, and embedder network. Minor gaps exist, such as the absence of an unsubscribe or delete-episode tool, but the core workflows are well-supported and agents can accomplish most tasks.