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

With readOnlyHint and openWorldHint already set, the annotation bar is low for safety. The description goes further by disclosing the payload shape: status enum values (unknown/up/down), uptime windows (24h/7d), and incident history including inbox and owner notifications. This adds meaningful context beyond the annotations, though nothing about freshness, ordering, or limits.

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 response contents are the opening clause. It reads as a compact list but every element earns its place given there's no output schema.

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 read-only tool with no output schema, describing the return contents is the key gap to fill, and this description does so well (status, results, uptime windows, incidents). It falls short only on pagination/volume and access scoping ('my' vs the required utility instance_id).

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 100%, so instance_id and passport_token are already documented in the schema. The description adds nothing about parameter meaning or format, so the baseline 3 applies.

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 establishes the resource (your watched URLs) and enumerates the returned facets (status, last results, uptime %, incidents). The action is implicit rather than a stated verb, but combined with the title it's unambiguous and distinguishable from the uptime_add/uptime_remove siblings that mutate the list.

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?

There is no when-to-use guidance, no mention of alternatives (uptime_add, uptime_remove), and no prerequisites even though an instance_id is required. An agent can infer it's a retrieval tool, but the description does nothing to route it against siblings.

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