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

With no annotations, the description carries the burden and does disclose active-event status, sources, return fields, and source TTL expiry. It omits rate limits or pagination and, more importantly, claims filtering behavior that the empty input schema cannot support.

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?

Front-loads purpose and sources, and most sentences add useful context. Some repetition around filtering and the sibling comparison could be tightened, but the structure is efficient.

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 zero-parameter, no-output-schema retrieval tool, it covers sources, return fields, and TTL expiry well enough. The missing piece is an accurate explanation of invocation: it should not promise filters that are unavailable, and it lacks operational limits.

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?

With zero parameters the baseline would be 4, but the description invents four filter controls (event type, country, region, lookback) that do not exist in the schema. This actively misleads an agent about how to invoke the tool.

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?

States a specific verb and resource ('Get active natural disaster events'), gives supply-chain scope, enumerates sources, and explicitly contrasts itself with get_natural_disaster_alerts. An agent can identify what the tool returns and how it differs from the sibling.

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?

Names the sibling get_natural_disaster_alerts and says this tool is for additional filtering such as multi-day lookback and region filtering. However, those selection criteria are not actually exposable because the input schema has zero parameters, making the guidance unreliable.

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