FREE feedback tool — after you have traded on (or evaluated) our signals, leave a rating: score 1-10 plus what was good (pros) and what to improve (cons). Costs nothing, no payment header needed. Helps us tune the signal engine.
| Name | Required | Description | Default |
|---|---|---|---|
| cons | No | What could be better | |
| pros | No | What you liked | |
| score | Yes | Overall score 1 (poor) to 10 (excellent) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries the transparency burden. It discloses that the tool is free ('costs nothing, no payment header needed'), which is valuable behavioral info. However, it does not mention any side effects, return behavior, or safety aspects beyond cost.
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, front-loaded with 'FREE feedback tool'. Every sentence adds value: purpose, when to use, parameter hints, and benefit. No unnecessary 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?
For a simple 3-parameter tool with no output schema, the description covers when to use and what to provide. However, it does not specify the return value or any confirmation of the rating submission, leaving a minor gap.
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 100%, so baseline is 3. The description reinforces the meaning of parameters (score 1-10, pros, cons) but adds little beyond the schema descriptions. It does provide context ('what was good, what to improve').
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 it's a feedback tool for rating signals after trading, with a specific verb 'leave a rating' and resource 'feedback'. It distinguishes from sibling tools like evaluate_symbol (analysis) and subscribe (subscription).
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 states 'after you have traded on (or evaluated) our signals', providing clear context for when to use. Does not list when not to use or alternatives, but the context sufficiently differentiates from siblings.
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: pitch for introduction, rate for feedback, subscribe for subscription management, evaluate_symbol for single-symbol analysis, and scan_bottoms/scan_tops for market-wide scans. No overlapping functionality.
Most tools use a verb or verb_noun pattern with lowercase and underscores where needed (evaluate_symbol, scan_bottoms). pitch, rate, and subscribe are single-word verbs, which is consistent in style. The mix is minor and still readable.
With 6 tools, the set covers the essential actions for a crypto signal service: introduction, single evaluation, market scanning, feedback, and subscription management. This is well-scoped and not overwhelming.
The major workflows are covered, including getting signals, scanning the market, and managing subscriptions. A minor gap is the lack of an explicit cancellation tool for subscriptions, but the existing tools provide a complete basic surface.