Your daily briefing at The Balanced Investor Club — a read on your own activity: morning brief, journal counts, the instruments you follow, mood highlights, activity, and your learning journey. A mirror, never advice.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds meaningful context by detailing the content scope (journal counts, followed instruments, mood highlights) and the nature of the output as a 'mirror' rather than advice. It does not disclose any other behavioral traits, but none are needed for a safe read-only operation.
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, each earning its place: the first front-loads the purpose and contents, the second clarifies the non-advice nature. No filler or redundancy; concise and well-structured.
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?
Understanding this tool requires knowing that it provides a personalized, aggregated daily briefing. The description covers the key output categories and the tone ('mirror, never advice'). With no output schema, this description gives enough context for an agent to invoke it appropriately and interpret its results.
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 tool takes zero parameters, so schema coverage is complete and no parameter documentation is required. The description adds value by explaining what the returned briefing contains, which fulfills the parameter-semantics baseline for parameterless tools.
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 provides a daily briefing on the user's own activity, enumerating specific sections (morning brief, journal counts, instruments followed, mood highlights, activity, learning journey). This distinguishes it from sibling tools like get_my_journal_stats or get_my_watchlists, which focus on single data types. The phrase 'A mirror, never advice' further clarifies its informational nature.
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 establishes clear context: this is a daily, personal briefing aggregating various aspects of the user's activity. It implies usage when an overview is needed rather than a specific data point, though it does not explicitly name alternatives. The 'mirror, never advice' wording provides a light constraint, but there is no explicit when-not-to-use guidance.
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.
With 57 tools, most have distinct purposes (market data, journaling, watchlists). A few related tools (get_price_alignment vs get_crypto_price_alignment, get_market_pulse vs get_market_movers) could cause miselection, but descriptions clarify asset types and scope.
Tools predominantly use get_/list_/create_/update_/delete_ verbs with clear noun suffixes. Minor deviations like start_here, whoami, add_to_watchlist, and remove_from_watchlist break the pure verb_noun pattern, but the style is consistent and readable.
At 57 tools, the server is far beyond the well-scoped range. While the domain is broad, this many tools will overwhelm an agent's capability to select accurately, and many could be consolidated (e.g., separate financial statements).
The server covers watchlist CRUD, trading journaling, market data (fundamentals, statements, news, transcripts), analysis tools, and community features. No obvious dead ends; lifecycle coverage is thorough for the described domain.
