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

With no annotations, the description carries the full burden. It discloses that `sources` defaults to all three and that sentiment is blended across platforms, which are behavioral traits. However, it does not explicitly state that the tool is read-only, nor does it mention rate limits or any side effects. For a sentiment query, read-only is strongly implied, so a 3 is appropriate for partial disclosure.

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 three short, front-loaded sentences: purpose, use case, and default. Every sentence adds value with no redundancy or fluff. It is exemplary in conciseness.

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?

The tool is simple, has an output schema, and the description covers purpose, usage, and the main default. It does not mention potential limitations (e.g., only US tickers) or exact source string formats, but these are minor for a sentiment tool. The presence of an output schema means return values are covered elsewhere, so the description is sufficiently complete for an agent to use it 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 compensate. It only explains the `sources` default and implies that it can be filtered to the three platforms mentioned. It does not elaborate on `ticker` (beyond the name) or `limit` (beyond the name), nor does it specify allowed values for `sources`. This is partial compensation, but not enough to fully cover the missing schema descriptions.

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 verb (blended) and resource (retail sentiment for a ticker) across three named platforms (X, StockTwits, Reddit), clearly distinguishing it from single-platform siblings like reddit_attention, stocktwits_symbol, and search_x. This is a precise purpose that leaves no ambiguity about what the tool does.

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 a clear use case: 'Use this to corroborate (or challenge) an analyst's view with the broader crowd.' This gives an agent context for when to invoke it. However, it does not explicitly mention alternatives or when not to use it, though the blended nature implies it is the go-to for cross-platform sentiment. This earns a 4 rather than a 5.

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