Get the latest research digest for an enrolled user. Returns filing signals, recent facts, stock quotes, and AI agent interest levels for their watched companies. Use this to brief a user on their portfolio.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | User email address |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Describes the read operation and the specific data returned (filing signals, facts, quotes, interest levels). With no annotations, the description adequately conveys behavior, though it does not mention error handling if the user is not enrolled.
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?
Three concise sentences: first states the action, second lists contents, third provides use case. No redundant 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 single parameter and no output schema, the description fully explains what the tool does and what it returns. Adequate for a digest retrieval tool.
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% (email parameter described). Description adds no extra semantics beyond what the schema provides, so baseline of 3 is appropriate.
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?
Clearly states the verb 'Get' and the specific resource 'latest research digest'. Distinguishes from siblings by specifying it returns a comprehensive digest of filing signals, facts, quotes, and interest levels, which is not provided by other origin_ tools.
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?
Explicitly says 'Use this to brief a user on their portfolio', providing a clear use case. Does not mention when not to use or alternatives, but the intended context is well-defined.
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: company lookup, digest, enrollment, filings index, person career, profile, search, timeline, and transcripts. No overlap in functionality.
All tools follow a consistent 'origin_' prefix followed by a descriptive word. The naming pattern is predictable and uniform across the set.
9 tools is appropriate for a filings and company research server. It covers core functionalities without being overwhelming or sparse.
The tool set covers the full domain of company research: lookup, profile, filings, transcripts, timeline, person career, cross-company search, digest, and user enrollment. No obvious gaps.