gdelt_tone_analysis

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

No annotations provided, so description must disclose behavior. It states it returns tone scores and timeline, implying a read-only analysis. However, it lacks details on rate limits, data source (GDELT), or response format, leaving gaps for heavy reliance on the tool.

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?

Two sentences, no fluff. Action and output are front-loaded. Every sentence adds value.

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?

For a simple analysis tool with 4 params (1 required), the description covers purpose, inputs, and outputs. It could mention the GDELT data source or response structure, but overall sufficient for an agent to invoke correctly.

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 has 100% coverage with clear descriptions for all 4 parameters. The description adds no extra meaning beyond 'topic' and 'over time', which are already implied by the schema. Baseline 3 is appropriate.

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?

Description clearly states the verb 'Analyse', resource 'global news coverage for a topic', and outputs 'average tone scores, trend summary, timeline'. It distinguishes from sibling tools like gdelt_news_search and gdelt_trending by focusing on sentiment analysis.

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 provides context ('Great for brand monitoring or tracking public sentiment') but lacks explicit guidance on when to use vs alternatives or when not to use. Could be improved by mentioning sibling tools like gdelt_news_search for raw news.

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