check_uptime

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

No annotations are provided, so the description carries the entire behavioral burden, and it discloses very little. It does not state that the operation is read-only, whether credentials/API access to Better Stack are needed, how much history 'recent downtime incidents' covers, or any rate limits. The word 'Query' hints at a read, but nothing is affirmed.

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?

A single front-loaded sentence with no filler; the resource and the three reported dimensions are packed in without redundancy. Nothing could be trimmed without losing information.

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 should ideally sketch the return shape (e.g., per-monitor status list, incident timestamps), and it only gestures at it via 'availability, status (up/down), and recent downtime incidents'. For a zero-parameter, zero-annotation tool it is workable but leaves the agent guessing about result granularity and time windows.

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 schema declares zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. Nothing in the description misdescribes the (empty) input surface.

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 pairs a clear verb ('Query', 'check') with a specific resource ('Better Stack Uptime monitors') and enumerates what it reports: availability, up/down status, and recent downtime incidents. That is far more specific than the vague sibling names like get_observability_status or get_production_health. It stops short of explicitly differentiating itself from those siblings, so it lands at 4 rather than 5.

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?

Use is implied by the stated scope (checking monitor availability and downtime incidents), but there is no explicit when-to-use, no when-not-to-use, and none of the many similar siblings (get_observability_status, get_production_health, correlate_incident) are named as alternatives. The agent must infer that this is the Better-Stack-specific path.

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