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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the data provenance (official status feeds only), the 7-day incident window, and the freshness caveat that feeds can lag.

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?

Three sentences, front-loaded with the resource and scope before the operational caveats; the provider enumeration is long but justified because it defines coverage boundaries. Every sentence carries information, though the parenthetical list is heavy.

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?

With no output schema, the description must convey what comes back, and it does: current status plus incidents from the last 7 days, with the default filter to non-operational providers. The only gap is the effect of include_incidents=false, which is undocumented in both description and schema.

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 coverage is 50%: 'provider' is documented in the schema with examples (openai, chatgpt, claude, grok, cursor), while 'include_incidents' has only a default and no explanation in either place. The description explains the provider-omission semantics but says nothing about what include_incidents=false returns, so it only partially compensates.

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?

Specific verb+resource (current status and incidents) with a precise scope: last 7 days, 17 named AI providers, sourced only from official status feeds. The enumerated provider list and the 'What Broke Today' attribution make it unmistakable, and it cannot be confused with any sibling (get_tool, search_tools, submit_field_report).

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?

'Omit provider to get only providers that are not fully operational' is an explicit behavioral rule for a key input decision, and 'Feeds can lag; quote the check time' tells the agent how to use the result responsibly. No explicit when-not-to-use or alternative tool is named, but none of the siblings overlap, so nothing is really missing.

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