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

With readOnlyHint and openWorldHint already declared, the description adds real operational context: 0.001 credits per call, a free no-credential tier capped at 25 calls/day per address, and the HTTP endpoint. Cost and rate-limit disclosure is exactly the kind of value structured annotations cannot carry.

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?

A single dense parenthetical with no filler — endpoint, cost, and quota are front-loaded after the one-line purpose. Efficient, though the nested parenthetical is slightly hard 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?

No output schema exists, so the description should describe what sentiment data comes back, and it does not. Combined with 0% parameter coverage on two enum params, an agent knows the cost and endpoint but not what it receives or how source/window change the result.

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 description coverage is 0%, so the description must compensate, and it does not. It only exposes the ticker via the URL template; the 'source' (reddit/stocktwits/combined) and 'window' (24h/7d/30d) enums are left entirely unexplained, along with their defaults.

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 names a specific resource (sentiment rollup for a ticker) and scopes it as value-investor-focused rather than WSB noise, which is a meaningful distinction. However, it never says what a 'rollup' actually contains (bullish/bearish score, post volume, etc.), so the purpose is clear at a high level but not precise.

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?

There is no when-to-use or when-not-to-use guidance, no mention of alternatives, and no prerequisites beyond the credential note. 'Not WSB noise' hints at positioning but does not tell an agent when to reach for this tool versus news, guru, or theses.

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