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

With no annotations, the description carries the full burden of explaining behavior. It discloses that posts are recent and include author-tagged labels, but it does not mention pagination, sort order, time range boundaries, or any limitations. The behavior is simple enough that this is adequate, though not rich.

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, tightly written sentence with no filler. The core subject, target, and differentiator (author-tagged bull/bear labels) are front-loaded efficiently.

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 simple schema and presence of an output schema, the description is minimally viable. However, it omits usage context relative to sibling tools and does not explain the limit parameter's role, leaving an agent to infer important selection and invocation details.

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. It clarifies that 'ticker' refers to the StockTwits posts target, but it says nothing about 'limit' beyond the schema's default value. The semantic of 'limit' is left entirely to the parameter name and default.

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 clearly identifies the resource (ticker) and the returned content (recent StockTwits posts with bull/bear labels). It does not use a strong verb like 'retrieve' or 'get,' and it does not explicitly distinguish itself from similar sibling tools such as ticker_social_sentiment, so it stops short of a 5.

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 about when to choose this tool over alternatives like ticker_social_sentiment or reddit_attention. The description states what the tool returns but provides no exclusions, prerequisites, or preferred use cases.

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