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

Annotations already declare readOnly, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavior beyond that: paid-plan gating for probe uptime, fixed 30-day windows, and 28/90/182 trend horizons. It stops short of describing pagination or response shape, but adds real context.

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 that enumerates distinct output components without filler. It is dense and slightly run-on, but every clause corresponds to a real section of the response, so little is wasted.

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 must carry the return-value burden, and it does so thoroughly: pass share, 30-day daily history, trend horizons, per-group briefings with cause and fix, and probe availability. Coverage of output is strong; only the absence of any usage/routing guidance holds it back.

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%, so both parameters are already documented, and the schema even gives the enum default. The description restates the 28/90/182 values in prose but adds no syntax or meaning beyond the schema's own "Trend length in days (default 28)". Baseline 3 is appropriate.

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 states the resource and what it conveys: a site's standing, pass share now and per-day, trends, group briefings and probe uptime. It references "the Overview's 'Monitors passing'" which implicitly ties it to the site_overview sibling, but it never names an alternative or explicitly says which tool to reach for, so differentiation is only partial.

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 when-not-to-use, and no mention of alternatives such as site_overview or get_performance. The content list implies the use case (assessing site health) but an agent gets no explicit routing help.

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