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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still earns credit by disclosing data provenance and reliability ('unverified claims, not news confirmation') and the feed source, which annotations cannot convey.

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?

Three tight sentences with no redundancy; the core purpose leads, followed by usage trigger, then the reliability caveat. Every sentence carries distinct information.

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?

With annotations covering safety and no output schema required to be explained, the description supplies purpose, usage context and a data caveat. The main remaining hole is parameter guidance for limit/includeReplies, which are undocumented in both schema and description.

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 coverage is only 25% — only 'hours' is documented, while 'limit', 'includeReplies' and 'ticker' have no schema descriptions. The description says nothing about any parameter, so it fails to compensate for the coverage gap on a 4-parameter tool.

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 gives a specific verb and resource ('Search ... recent X posts about a ticker') and adds a scoping detail ('the same cashtag feed as TWIT'). It is clearly distinct from news tools, but it never names its closest sibling social.search_posts, so the agent must infer which social search to pick.

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?

'Use this when asking what traders are saying or looking for a possible catalyst' states the triggering intent clearly. It stops short of exclusion guidance, e.g. when to use social.search_posts or news.stories instead, so routing between sibling tools is left partly to inference.

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