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

With no annotations, the description carries the full burden. It discloses the 24-hour time constraint, which is useful, but does not mention response format, rate limits, pagination, or query syntax nuances. The behavioral disclosure is minimal and incomplete for a tool lacking any structured safety hints.

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 entire description is a single, front-loaded sentence with no fluff. Every word earns its place, conveying resource, scope, and the query mechanism efficiently.

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 parameter tool with an output schema, the description covers the core function and time window. It omits guidance on when to choose it over other news-related siblings and does not state any usage prerequisites, but given the low complexity and existing output schema, this is minimally adequate.

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 schema has one parameter 'q' with zero description coverage. The description's phrase 'by keyword' informs that 'q' is a keyword search term, adding basic meaning beyond the schema's bare string type. However, it does not provide formatting details, wildcard support, or boolean operators, so compensation for the coverage gap is partial.

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 'GDELT News: Global news/events by keyword (last 24h)' names the specific resource (GDELT news/events) and scope (last 24h), and 'by keyword' clearly signals a queryable search. It distinguishes itself from the many sibling tools by referencing GDELT explicitly, though it lacks an explicit verb like 'search'.

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 versus alternatives is provided. The description does not mention any exclusions, preferred contexts, or related search tools, leaving the agent to infer that it should be used when GDELT news data is needed.

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