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

Beyond the annotations, the description discloses authentication requirements, shared refresh throttling, freshness handling, return contents, unresolved-entry behavior, Google informational notices, coverage.scope inspection, and untrusted-text handling. This is unusually rich behavioral context for an open-world read tool.

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 key purpose and caveats are front-loaded, and most sentences carry operational value. It is slightly longer than necessary because the provider list duplicates the schema enum and several clauses could be tighter, but there is little wasted content.

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 one-parameter, open-world incident tool with an output schema, the description supplies the important operational context: freshness, staleness semantics, coverage limits, trust boundary, and Google scope separation. An agent has enough information to invoke it correctly without relying on the return schema alone.

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?

Schema description coverage is 0%, and the description largely repeats the enum provider names rather than explaining the provider parameter directly. It does add one important semantic distinction: Google sources are separate product scopes, not a single all-Google or Gemini verdict.

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 opens with a specific verb and resource: official active incident reports, scoped to named providers. It is immediately distinguishable from siblings like get_service_status and list_monitored_services because it names the exact provider-status source set and says these are unresolved official entries.

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?

It clearly establishes when to use the tool: for official active incidents from the listed providers, with explicit cautions that missing/stale data means unknown rather than all-clear. It does not name alternative sibling tools or explicitly state when not to use this tool, so it falls short of full alternative routing.

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