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

No annotations are provided, so the description must carry the behavioral disclosure burden. It adds useful context about the source and time sensitivity, but it does not clarify how 'most-mentioned' is computed, whether the data is live or delayed, or whether this is purely a read-only call. This is adequate for a simple listing tool but not deeply transparent.

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 a single compact sentence with the core purpose front-loaded. The parenthetical adds source and use-case context without unnecessary words or repetition.

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 simple one-parameter tool with an output schema, the core purpose is clear. However, the description lacks explicit usage guidance, sibling differentiation, and parameter explanation, leaving some important context to inference. It is adequate but has clear gaps.

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%, and the description does not mention the 'limit' parameter or its meaning. The schema provides type and default, but the description adds no semantic elaboration to help an agent understand how the limit affects the returned list.

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 exactly what the tool returns: the most-mentioned tickers on r/wallstreetbets right now, and identifies the data source (ApeWisdom). This is specific enough to distinguish it from broader sibling tools like reddit_attention or trending_tickers.

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 phrase 'retail-attention radar' implies the intended use case, and 'right now' suggests it is for current interest. However, the description does not explicitly say when to use this tool instead of similar alternatives such as reddit_attention or trending_tickers.

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