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

With no annotations, the description discloses tone range and output granularity, but omits potential side effects, authentication needs, or error handling. For a read-only analytics tool, it is adequate but not detailed.

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?

Single sentence, front-loaded with purpose, and no unnecessary words. It efficiently conveys the core idea.

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 4 parameters and no output schema, the description leaves gaps: no description of country, timespan, or query format. Output is partially described but not complete (e.g., pagination, date range).

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%, so description must compensate. It only clarifies granularity ('hourly or daily') and implies query usage. Does not explain country, timespan format, or query syntax.

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 a sentiment-tone timeseries for a query, with average tone and volume per time step. It implicitly distinguishes from siblings by specifying aggregated temporal output, but lacks explicit comparison.

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?

No guidance on when to use this tool vs. siblings (gdelt_search_events, gdelt_trending_actors). The description does not mention use cases or exclusions.

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