segnals_get_sentiment

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses that the tool is 'coming soon' (unavailable endpoint) and requires the 'read:news' scope, which provides useful behavioral context. However, it does not explicitly state that the operation is read-only or non-destructive, nor does it describe any side effects. With no annotations, the description partially compensates but lacks full transparency.

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 four sentences, front-loading the purpose and following with a note and example. It is concise and avoids unnecessary detail. The 'coming soon' warning is critical but could be integrated more succinctly. Overall well-structured for the information provided.

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 no output schema, the description only vaguely mentions 'bullish/bearish sentiment indicators' without specifying return format, data structure, or time range. The tool is simple (1 param), but the lack of output details and behavioral expectations (e.g., rate limits) leaves gaps. The 'coming soon' status also reduces immediate completeness.

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% for the single 'symbol' parameter, so the baseline is 3. The description adds an example ('BTCUSDT') and clarifies the parameter is for a 'specific coin or trading symbol', adding minimal value beyond the schema. No additional semantic details are provided.

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 retrieves market sentiment data for a specific coin or symbol, indicating bullish/bearish sentiment. The verb 'Get' is specific, and the resource (sentiment data) is well-defined. However, it does not explicitly differentiate from sibling tools like segnals_get_news or segnals_get_market_price, though the unique focus on sentiment is implied.

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?

No guidance is provided on when to use this tool versus alternatives such as segnals_get_news or segnals_get_market_price. There are no context cues about prerequisites, use cases, or exclusion criteria beyond the scope requirement. The 'coming soon' note indicates unavailability but does not assist in tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.