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

With no annotations provided, the description bears the full responsibility for behavioral disclosure. It only says 'currently trending' without explaining what 'trending' means algorithmically, whether the list is a snapshot or has pagination, any rate limits, or what fields appear in the output (beyond tickers). The 'retail-attention radar' phrase adds a hint but does not disclose concrete behavioral traits.

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 efficient—a single sentence with no fluff. It front-loads the core purpose and adds a clarifying metaphor. However, it is arguably too terse, omitting substantial operational detail, so it leans toward under-specification rather than ideal conciseness.

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 presence of many sibling attention-tracking tools and an output schema (though not visible), the description should clarify what the tool returns and how it differs. It neither explains the parameter nor disambiguates from alternatives, nor describes the output structure. For a tool with minimal annotations, this level of detail is inadequate.

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 single parameter 'limit' has no description in the schema (coverage 0%) and the tool description does not mention it at all. An agent seeing 'limit' with a default of 30 has no idea it controls the number of results or how it affects the output. With zero schema coverage and zero description coverage, this is a complete gap.

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 states a clear verb (trending) and resource (StockTwits tickers), and adds the useful characterization 'retail-attention radar' to convey the data's nature. It does not explicitly contrast with sibling tools like wsb_trending or reddit_attention, but the platform name (StockTwits) inherently distinguishes it from those, so it is clear though not fully differentiated.

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 given on when to choose this tool over the many similar siblings (wsb_trending, reddit_attention, leaderboard). There is no mention of context such as 'use for StockTwits-specific retail sentiment' or exclusions. The agent must infer usage from the platform name alone, which is insufficient given the abundance of alternative attention-tracking tools.

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