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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context about the data source ('Backed by ApeWisdom'), the 24h timeframe, and the interpretive caveat ('often a contrarian/risk flag, not a buy signal'). However, it does not state whether the operation is read-only, what counts as a mention, or any access/rate considerations.

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 short and front-loaded, with the first sentence delivering the core purpose and the second adding interpretation. Both sentences earn their place, though the interpretive guidance could arguably be tighter.

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, so return-value detail is not the description's job. The description covers the data source and interpretive meaning, but it lacks sibling differentiation and any mention of the time window beyond '24h momentum' or how the rank is scoped. It is adequate but leaves selection context incomplete.

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?

There is only one parameter, 'ticker', and schema description coverage is 0%. The description merely repeats the concept of 'a ticker' without adding format, examples, or constraints. Given the total lack of schema descriptions, the description should have compensated with at least a symbol format hint or example.

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 specific resource ('WSB retail-attention for a ticker') and the core outputs ('mention count, rank, and 24h momentum'). It is clear and informative, though it does not explicitly contrast with siblings such as wsb_trending or ticker_social_sentiment.

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 use case is implied: use when you need Reddit/WSB retail-attention metrics for a specific ticker. However, there is no explicit guidance on when to prefer this tool over sibling tools like ticker_social_sentiment or wsb_trending, and no exclusions are stated.

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