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

With no annotations, the description carries the full burden. It does disclose the nature of the result (ranked tickers, bull/bear ratio, directional bias), which implies a read-only scan, but says nothing about data freshness, which subreddits or time window are covered, rate limits, or any auth requirement.

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 compact sentences, front-loaded with what the tool returns and followed by when to use it. Minor redundancy in repeating 'crypto sentiment' / 'crypto social feeds', but no filler.

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 zero-parameter tool with no output schema and no annotations, the description should describe the shape and scope of what comes back. It names the ranking metric and bias fields but omits any time window or coverage scope, which materially affects how an agent interprets a sentiment read.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. Description correctly requires no inputs, consistent with the empty schema.

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?

States a specific resource and operation: a Reddit crypto sentiment scan producing top tickers ranked by bull/bear ratio with LONG/SHORT bias. An agent can tell this is a sentiment/positioning read rather than a market-data or signal-execution tool, though it never names which sibling to prefer over it.

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?

Gives explicit trigger conditions — social sentiment, crowd positioning, bullish/bearish read — which is clear usage context. It stops short of exclusions or pointing to alternatives (e.g. akari_feed or akari_confluence) for adjacent needs.

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