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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description correctly spends its words on content: the response carries status and last check, child content checks/dependencies/cron jobs with last and next runs, SSL and domain expiry, anomaly detection, maintenance in the next 7 days, and open incidents. It does not mention cost, latency, or size of the payload, which is the main remaining gap for a detail endpoint that fans out into children.

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 usage condition and the exclusion are front-loaded, which is the right order. The middle sentence is a long semicolon-chained inventory of return fields; it earns its place because no output schema exists, but it is dense enough to be slightly hard to scan.

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 takes on the full burden of explaining what comes back and does so in detail, including how the include sections modify the payload. Combined with the readOnly annotations and the routing guidance, an agent has everything needed to call this correctly.

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 coverage is 100%, and the schema already defines 'site' (id, name, or partial URL) and each include enum value. The description restates the include behavior with a little extra color (which issuers the site expects) but adds no syntax or format guidance beyond the schema, so the baseline of 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 names the resource (one site) and enumerates the concrete questions it answers: is it up, why is it down, what is checked, when the certificate or domain expires. It also explicitly separates itself from get_monitor_history and get_report, so an agent can route without opening the 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?

It gives an explicit trigger condition ("Use this when the user asks about one of their websites or APIs") and an explicit exclusion with named alternatives for the out-of-scope case ("Not for past checks or uptime over a range: use get_monitor_history or get_report"). Nothing is left to inference.

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