news_sentiment

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

Discloses auto-routing for crypto queries and details return fields including scales. No annotations provided, so description carries full burden and does so effectively.

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 sentences front-loaded with purpose. No wasted words. Perfectly concise for the information conveyed.

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?

Output schema exists (implied), description covers return fields, usage context, and special behavior. Complete for a simple parameter tool.

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?

Single 'query' parameter with 0% schema coverage. Description gives examples (stock ticker or crypto asset) but no exact format or constraints. Adequate but not comprehensive.

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?

Clear verb 'returns sentiment' and resource 'news'. Specific outputs listed. Distinguishes from siblings like equity_analysis by focusing on news sentiment.

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?

Explicit use case 'before a trade to detect sentiment regime or monitor news flow'. Pairs well with three sibling tools, providing context for when to use.

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