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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it mentions the data scope (recent posts with labels), it omits key traits such as read-only nature, authentication requirements, rate limiting, pagination, or what 'recent' means. The description is insufficient for an agent to understand behavioral constraints.

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 sentence that conveys the core purpose without any filler. It is front-loaded with the key action and resource, achieving maximum conciseness for the information provided.

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 tool's simplicity (2 parameters, no annotations) and the presence of an output schema, the description lacks completeness. It does not explain what 'recent' means, how labels are presented, or how the 'limit' parameter affects results. The output schema may cover return format, but the description should provide more operational context for an agent to use the tool correctly.

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 add meaning. It explains 'ticker' (required stock symbol) but says nothing about 'limit' besides its default in the schema. The description partially compensates by clarifying the role of the ticker, but leaves the 'limit' parameter undefined, forcing agents to infer from the name.

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 states the resource (StockTwits posts for a ticker) and the data included (author-tagged bull/bear labels). However, it lacks an explicit action verb like 'get' or 'list', which slightly reduces clarity. It distinguishes from sibling tools like 'reddit_attention' and 'ticker_social_sentiment' by focusing on StockTwits with labels.

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 provided on when to use this tool versus alternatives such as 'reddit_attention' or 'ticker_social_sentiment'. There is no indication of prerequisites, limitations, or exclusions. The description solely states what it does, not when to choose it.

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