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

Annotations already cover read-only and open-world behavior, but the description meaningfully adds pricing ($0.002 USDC per successful call via x402 on Base, Solana, or Arc) and states failed calls are not charged. It also discloses the data source (social posts) and a caveat that it is not a recommendation—material context beyond annotations.

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?

Three sentences front-load purpose, then caveat, then pricing, with no wasted wording. The structure lets an agent immediately understand what the tool returns and what it costs.

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?

An output schema exists, yet the description still names key returned fields for quick orientation. It covers cost, data source, and a caution, which is sufficient for a read-only tool with one optional parameter.

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 100%, with the single limit parameter fully documented in the schema as 1–30 with a default of 10. The description adds no parameter-level detail, so the baseline of 3 is appropriate.

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 verb and resource ('Stocktwits trending stock symbols right now') and enumerates returned fields (ticker, company title, exchange, watchlist count, trending score). No sibling tool covers social-sentiment trending symbols, so it is clearly distinguishable from the crypto and finance alternatives.

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?

The description provides context ('right now', 'a popularity list from social posts, not a recommendation') but does not explicitly say when to use this tool versus other finance tools or name alternatives. Usage is implied rather than prescribed, leaving the agent to infer the appropriate case.

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