show_world_intel

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

With no annotations, the description carries the full burden. It discloses that no API keys are required and shows all active alerts with Orange+ default. However, it does not mention rate limits, data freshness, or output format, leaving some gaps for an AI agent.

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 description is three sentences, front-loaded with the main purpose, followed by constraints and examples. It is efficient with no wasted words, though slightly more structure could improve scannability.

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 no output schema, the description should detail return format. It mentions 'shows all currently active alerts' and lists macro indicators, but lacks explicit structure or pagination info. Input parameters are well-covered, so overall it's adequate but not fully detailed.

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?

Both parameters have descriptions in the input schema (100% coverage), so the baseline is 3. The description adds context about default behavior and output scope but does not significantly enhance parameter meaning beyond the schema.

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 the tool provides a global intelligence drill-down combining World Bank macro data (GDP growth, inflation, unemployment per country) and GDACS active disasters (Orange/Red alerts). It distinguishes itself from siblings by recommending usage after get_brief and providing specific example queries.

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 explicitly says 'Use after get_brief when you need more detail on global risks' and gives concrete examples like 'which countries are in recession'. It does not specify when not to use it or compare to other sibling tools like show_macro, but the context is clear enough.

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