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

Annotations only declare read-only/open-world/non-destructive; the description goes well beyond by disclosing that it fetches from six regions, needs no sign-in, stores nothing about the user, and caches results per site for a day. Those are exactly the operational facts (privacy, freshness, cost) an agent cannot infer from the annotations.

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?

Front-loaded with the trigger conditions, then behavior, then exclusions, then a doc link — a sensible ordering with essentially no filler. It is a single dense paragraph of considerable length, though, and would scan faster split into use/not-for/behavior lines.

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 carries the return-value burden itself and does so thoroughly: recognized services with per-service evidence and current status, certificate expiry, DNS summary, current uptime, viable page checks, and a per-plan monitor count. Combined with the caching and no-sign-in notes, an agent has everything needed to set expectations before calling.

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?

There is a single parameter at 100% schema description coverage, which already documents accepted forms like 'https://example.com or example.com'. The description adds no further input guidance such as whether paths, ports, or non-HTML endpoints are accepted, so it neither helps nor hurts beyond the schema baseline.

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?

States a specific verb and resource (recommend what to monitor for a website) plus the concrete inputs it inspects (DNS records, home page, certificate) and the outputs it produces. It explicitly names the siblings it is not (check_service_status_url, and the signed-in plan/create tools), so an agent can distinguish it without opening any schema.

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?

Opens with the exact user phrasings that should trigger it ('what should I monitor', 'what could take their site down', 'which third-party services a site depends on') and adds the pre-signup evaluation case. It also gives explicit exclusions with named alternatives: check_service_status_url for a bare up/down check, and the account plan/create tools once signed in.

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