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

With no annotations, the description carries the full burden of behavioral disclosure. It transparently explains what data is returned (categorized alerts, severity, stage, risk score) and highlights the tiered behavior: 'Free tier returns critical-severity alerts only; paid tier returns all severities.' This goes beyond a simple 'get' and is useful for setting expectations. It does not mention rate limits or auth, but for a no-parameter read-only style tool, this is sufficient.

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 uses three sentences with no wasted words. It front-loads the core purpose ('Get real-time supply chain disruption alerts'), then details the output categories and fields, and finally explains tier limitations. Each sentence contributes meaningful information, making it highly concise and well-structured.

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 tool with no parameters and no output schema, the description is remarkably complete. It names the source (news intelligence and event detection), enumerates all alert categories, describes the per-alert structure (severity, stage, risk score), and clarifies tier-based content. There is no obvious missing context that would hinder correct invocation or interpretation of results.

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 input schema is an empty object (0 parameters), so the baseline is 4. The description adds no parameter-specific semantics because there are none to describe. It does mention the tier behavior which could be seen as a contextual option, but not a parameter. Given the zero-parameter schema, the description sufficiently covers the tool's invocation needs.

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 'Get real-time supply chain disruption alerts from global news intelligence and event detection.' It lists specific categories (port closures, trade policy, etc.) and return fields (severity, stage, risk score), distinguishing itself from sibling tools that focus on individual categories. The verb 'Get' plus the comprehensive resource makes the purpose unambiguous.

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 implies usage by showing it covers multiple disruption categories, but it does not explicitly say when to use this tool versus alternatives. There is no mention of exclusions or guidance like 'for a specific category use get_disaster_events'. The tier behavior (free vs paid) is a usage nuance but does not clarify tool selection. Thus, only implied usage guidance is provided.

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