forecast_regions

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

Describes the output (ranked regions and top countries) and implies a read-only aggregation. No annotations provided, so description carries full burden; lacks details on data freshness, update frequency, or any side effects.

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 concise sentences with no wasted words. Front-loads the core capability and usage recommendation.

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?

Sufficiently complete for a parameterless tool with no output schema. Tells agent what to expect from the response, though could mention the absence of input requirements explicitly.

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?

No parameters exist, so baseline is 4. Description adds meaning by explaining what the tool produces without needing input.

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?

Clearly states it aggregates a shutdown-risk forecast leaderboard across UN sub-regions, returning ranked regions and top countries. Distinguishes from sibling 'forecast_region' by emphasizing global coverage.

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?

Explicitly advises 'Use for a global regional overview in one call.' Provides clear context but does not explicitly exclude other tools or mention alternatives.

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