List Zipp's daily Editor Digests — market briefings written by named editorial personas, each synthesising the last 24h. Newest-first. Each item carries the editor, headline, standfirst, sentiment, and tickers covered; call get_digest(editor, date) for the full body.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | en-US | |
| limit | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses ordering (newest-first), what fields each item carries (editor, headline, standfirst, sentiment, tickers), and that full body requires a different call. This is strong transparency, though it could mention if there are limits or side effects beyond the trivial.
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 compact (two sentences), front-loaded with the tool's purpose, and every sentence adds value—no redundancy or fluff.
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 low complexity (0 required params, no enums) and presence of an output schema, the description is fairly complete: it covers output structure, ordering, and sibling relationships. It doesn't mention pagination beyond the limit default, but the output schema likely handles that.
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%, yet the description adds no information about the lang or limit parameters. The agent must infer from defaults and names; no format, constraints, or usage hints are provided. The description fails to compensate for the schema's lack of 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 tool lists daily Editor Digests, describes their content (market briefings, editorial personas, 24h synthesis), and explicitly distinguishes from sibling get_digest by noting that get_digest is for full body retrieval.
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 tells when to use this tool (list digests) and when to use a different tool (call get_digest for full body), providing clear usage guidance and an alternative.
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 targets a distinct content type or operation (e.g., breaking news vs. latest news, digests vs. guides, token snapshots vs. rankings). Descriptions clearly differentiate purposes, so an agent can easily select the correct tool.
All tools use snake_case with a verb_noun pattern, primarily 'get_*'. The exceptions are 'list_categories' and 'search', which are still clear but break the 'get_' prefix consistency.
With 13 tools, the server covers a broad but focused set of crypto news, education, and market data operations. The number feels appropriate for the domain—not too few to be incomplete, not too many to be overwhelming.
The tool surface provides comprehensive read-only access to news (latest, breaking, featured), editor digests, learn guides, token snapshots, rankings, trending tokens, and search. There are no obvious missing operations for consuming crypto content.
