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

With no annotations, the description carries the full burden and does disclose notable traits: $0.00 over MCP versus $0.002 over REST, sub-50ms latency, free during active outages, and the two data sources behind the verdict. It omits what the response contains and whether it is read-only, which keeps it short of a 5.

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?

Two dense sentences with the cost/latency hook front-loaded and the trigger conditions immediately after. Every clause carries information, though the pricing parenthetical is slightly bulky for the space it occupies.

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 single-parameter diagnostic with no output schema, the agent still has no idea what comes back — a boolean, a status enum, a list of incidents, or a recommended action. The description covers when to call and what data feeds the check but leaves the return contract entirely unstated.

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?

Only one parameter and schema coverage is 100%, so the schema already documents 'domain' fully. The description's example hostnames (api.openai.com, api.stripe.com, mainnet.base.org) reinforce the same examples already present in the schema, adding no new semantics such as accepted formats or subdomain handling.

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 names the resource (upstream host status) and the mechanism (Statuspage feeds plus a 5-minute agent swarm error velocity), and gives concrete example hosts. It never states plainly what the tool returns, but an agent can infer it is an upstream outage check and distinguish it from the sibling fix/diagnose tools.

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?

Trigger conditions are explicit and concrete: HTTP 5xx, timeout, or sudden auth/RPC failure against external hosts, with the purpose spelled out (halt destructive local edits during outages). No when-not conditions or named alternatives are given, but the sibling tools serve unrelated purposes so little ambiguity remains.

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