get_social_sentiment

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

No annotations provided; description explains scraping, classification, signal generation, and fallback behavior. Does not discuss rate limits or potential errors, but covers main behavioral aspects.

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?

Well-structured with front-loaded summary, but includes lengthy setup instructions; could be slightly more concise.

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?

Covers input, output, fallback, and setup. Lacks details on error handling or invalid inputs, but overall sufficient for the tool's complexity.

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 0%, but description explains symbol as NSE stock symbol and limit with default 100 and max 200, adding significant value beyond 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?

Clearly states it analyzes social media sentiment for NSE stocks using Reddit and Twitter, specifies subreddits and fallback, and distinguishes from siblings like market_news.

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?

Implies usage for sentiment analysis but lacks explicit when-to-use alternatives. Mentions fallback to yFinance if social APIs not configured, providing context.

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