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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it returns raw tweets, mention counts, price snapshots, a coverage block for upstream failures, and a billing block. It also explicitly states the tool does NOT rank or interpret, which prevents misuse. Minor gap: no mention of rate limits or pagination, but the coverage/billing disclosure is strong.

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 well-structured and front-loaded with the core value proposition. It uses short paragraphs and bullet-like lists to convey the workflow, return contents, and exclusions. Every sentence earns its place, and the explicit 'does NOT' clarification prevents misinterpretation.

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 has an output schema, so return values are documented elsewhere. The description covers the workflow, the joined data, the coverage/billing blocks, and the non-interpretation caveat. It lacks explicit mention of pagination or rate limits, but for a read-only aggregation tool with an output schema, this is nearly complete.

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 explains the overall flow (topic → cashtags → prices) and mentions 'most-mentioned symbols' which maps to max_tickers, and 'optionally recent company news' which maps to include_news. However, it does not explain the format of `since` (e.g., '7d' default) or the exact semantics of max_tickers beyond 'most-mentioned'. The description adds meaning but leaves some parameter details to the schema.

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 tool's function: it searches X/Twitter for a topic, extracts $TICKER cashtags, fetches price snapshots, and optionally news, then returns a joined bundle. It distinguishes itself from siblings by explicitly naming alternatives like get_twitter_tweet_advanced_search and get_financial_prices_snapshot.

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 explicitly states when to use this tool ('when you need the posts AND the market data behind them together') and when not to use it, naming the alternatives for posts-only or known-symbols cases. It also explains the manual multi-step alternative, making the tradeoff clear.

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