is_the_internet_on_fire

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds important presentation behavior: 'Lead with the overall picture... do NOT list every service. Only call out services that are NOT operational or have unknown status.' This is a useful behavioral trait. However, it does not mention whether the tool performs external network calls, whether it can be slow, or any side effects. Since it's a read-only health check, this is acceptable but not rich enough for a 4.

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, each earning its place: purpose, when to use, and how to present results. It is front-loaded with the primary action, and the additional presentation instructions are relevant and concise. It could be slightly tighter by merging some ideas, but overall it is well-structured and not wasteful.

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 1 optional parameter and no output schema, the description is contextually complete. It explains what the tool does, when to invoke it, and how to present the results. The absence of an explicit return format is not a significant gap since the presentation instructions effectively describe the expected output behavior. Sibling differentiation is not required for completeness.

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 covers 100% of the parameter semantics, including the description 'Filter to a specific category of services. Omit for all.' The tool description itself does not add any parameter-level detail. Per the rubric, with high schema coverage, the baseline of 3 is appropriate.

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's purpose: 'Check the health of major internet infrastructure and services.' It uses a specific verb ('check') and resource ('major internet infrastructure and services'), and the scenarios ('unexpected API errors, connection timeouts, degraded responses') further clarify its scope. It distinguishes itself from siblings by addressing broad infrastructure health rather than personal mood or a specific service status.

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 provides explicit when-to-use guidance: 'Call this when you encounter unexpected API errors, connection timeouts, or degraded responses from cloud services.' It also gives example user queries ('is AWS down?'). However, it does not mention any when-not-to-use scenarios or explicitly name alternative sibling tools, so it misses the full 5.

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