get_news_sentiment

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

The description adds context that the data is 'AI-powered from Perplexity' and 'daily', but lacks details on behavioral traits such as rate limits, data freshness guarantees, or cost implications. Annotations already indicate read-only and idempotent, so the description provides minimal extra behavioral insight.

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 concise with the key information front-loaded. The first sentence captures the core function. The inclusion of a redundant Vietnamese phrase slightly reduces conciseness but does not significantly hinder understanding.

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?

Given the lack of an output schema, the description partially covers the return values (bullish/bearish/neutral % and top events) but does not describe the exact output structure. For a tool with two optional parameters and no output schema, more detail on the response format would improve completeness.

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?

The input schema already fully describes the two parameters (symbol and days) with clear descriptions. The description does not add any additional meaning or usage guidance beyond the schema, so it meets the baseline with 100% schema coverage.

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 it returns daily news sentiment scores per ticker, including bullish/bearish/neutral percentages and top events. It also mentions AI-powered from Perplexity, distinguishing it from sibling tools like get_opinion or get_market_snapshot which serve different purposes.

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 implies usage for obtaining news sentiment for a ticker or market-wide, but it does not explicitly state when to use it versus alternatives or provide exclusion criteria. No guidance on when not to use this tool.

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