START HERE — your first call to this agent MUST be pitch (free, no payment). Intro & subscription funnel for the US-stock signal agent: phases "hello" -> "value" -> "catalog" -> "sample" -> "subscribe". Pass interest:false to bow out.
| Name | Required | Description | Default |
|---|---|---|---|
| phase | No | ||
| symbol | No | Symbol for the "sample" phase. The free sample serves only this market’s showcase symbol (NVDA); any other symbol is answered by the paid evaluate_symbol (x402). | |
| interest | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description reveals the tool's nature: free, multi-phase funnel, and option to exit via interest:false. However, it does not disclose potential side effects (e.g., state persistence) or behavior if phases are called out of order, leaving minor gaps.
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) and front-loaded with 'START HERE'. It packs significant information but could benefit from clearer separation of the four usage scenarios. Still, it is efficient and mostly easy to parse.
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 three-parameter complexity and no output schema, the description adequately covers the funnel flow, parameter semantics, and boundary conditions. It lacks details on expected return values or error handling, but the core interactions are sufficiently specified.
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?
Despite only 33% schema description coverage, the description richly explains each parameter: phase enum meanings, symbol's role limited to sample phase with NVDA constraint, and interest usage. This fully compensates for schema gaps and adds crucial context.
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 that this is the entry point to the agent, must be first call, and outlines the subscription funnel phases. It distinguishes itself from siblings by being the mandatory starting point and referencing evaluate_symbol for specific symbol needs.
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 instructs to use pitch as the first call, describes when to pass interest:false to bow out, and clarifies that only the sample phase uses a symbol and that other symbols should use evaluate_symbol. Provides clear when-to-use and 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.
Each tool has a clear, distinct purpose: pitch for intro, rate for feedback, evaluate_symbol for single symbol analysis, scan_bottoms and scan_tops for market-wide scans. No overlap or ambiguity.
All tool names use a consistent snake_case pattern, with clear verbs (evaluate, scan, pitch, rate) and nouns (symbol, bottoms, tops). The pattern is predictable and easy to understand.
With 5 tools, the set is well-scoped for the server's purpose of providing US stock signals. It covers introductory, analytical, scanning, and feedback functionalities without being excessive.
The tool set covers the core workflow: pitch (intro), evaluate_symbol (single symbol), scan_bottoms/scan_tops (market scans), and rate (feedback). Minor gaps like historical data or alerts exist, but the core signal service is complete.