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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses important behavioral traits: it loads nothing, costs no page allowance, adds/removes no pages, and shows the last recorded attempt rather than live site state. It also explains the ~20h monitoring cadence and the way silent failures can resemble clean sites, giving the agent deeper operational understanding.

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 description is longer than average, but every sentence earns its place: usage trigger, uniqueness, returned fields, slot reporting, read-only semantics, and cadence context. It is front-loaded with the most important usage guidance and contains no fluff or tautology.

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 one-parameter read-only tool with no output schema, the description is remarkably complete. It tells the agent when to call it, what data it returns, how to interpret empty results, what operational behavior to expect, and how to distinguish normal cadence from faults. Nothing essential is missing.

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%, and the schema already defines 'website' as the registered domain with an example. The tool description does not add new parameter-level meaning beyond that, so the baseline of 3 for high schema coverage 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 uses a specific verb ('lists') and resource ('monitored-page inventory for a website'), then enumerates exactly what is reported: watched URLs, paused pages, last scan time, last score, and failing/unreachable/throttled/overdue statuses. It also explicitly distinguishes itself as the only tool that reveals whether monitoring is actually working, separating it from siblings like list_websites or site_overview.

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?

The description gives an explicit trigger: 'Use this whenever a scan-backed answer came back empty or thin and you need to know whether that means clean or never checked.' It further states this is the only tool that reports whether monitoring works, which excludes alternatives, and warns that recent scans being 'due' is normal rather than a fault, shaping correct interpretation.

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