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

Annotations already declare readOnlyHint=true, so safety is covered. The description's real value-add is disclosing the auth-conditional result set (anonymous vs x-api-key holders unlock 0-100 conviction, 24h momentum, confidence breakdowns) and the data elements returned. It still says nothing about behavior for unknown tickers, latency, or caching.

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?

Two tight sentences, zero filler, with the core capability front-loaded and the access-tier caveat second. Nothing in it is redundant with the title.

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?

No output schema exists, so the description carries the burden of describing returns, which it partially does by naming conviction scores, momentum deltas, and confidence breakdowns. For a one-parameter read tool that is close to sufficient; missing only failure modes for invalid tickers.

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 100% for the single ticker parameter, including length constraints and its own examples, so the description does not need to compensate. Its 'e.g. NVDA, AAPL' restates the schema rather than adding format guidance, keeping this at the baseline-plus level.

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?

States a specific verb (aggregate) and a clearly scoped resource (swarm sentiment, conviction scores, discussion references) for a ticker symbol, with concrete examples. No sibling in the list overlaps with sentiment retrieval, so the agent will not confuse it with get_thread, search_feed, or vote, though the description never says so explicitly.

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?

Usage context is only implied: the second sentence signals that unauthenticated callers get a reduced payload and that an x-api-key unlocks the numeric metrics, which hints at the tiered-call situation. There is no explicit statement of when to use this versus search_feed/ask_marx_pro for sentiment-type questions, and no prerequisites or exclusions.

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