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

Annotations only declare readOnlyHint=true, and the description adds substantive behavior: the returned record fields are enumerated (grade, last/next scan, uptime, CVE alerts, new problems, cert expiry), which substitutes for the missing output schema. It does not mention pagination, ordering, or auth needs, keeping it short of a 5.

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?

Two dense sentences with the subject front-loaded and no filler; the field enumeration carries real information given there is no output schema. The comma-separated field list is slightly dense but nothing 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?

For a zero-parameter read tool with no output schema, the description supplies the one thing structured data cannot: what each monitor entry contains. Missing only operational details like result ordering or pagination, which are minor here.

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?

The tool takes zero parameters, so the schema has nothing to document and the baseline for this dimension is 4. The description correctly introduces no parameter syntax or confusion.

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 (sites under continuous monitoring) and enumerates exactly what each entry contains — grade, scan times, uptime, CVE alerts, findings, cert expiry. That is far more specific than the title, and the closing reference to monitor_scan_now hints at its role versus siblings, though it does not explicitly contrast with list_recent_scans or get_scan_status.

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 line 'Use the monitor id with monitor_scan_now' tells the agent what to do downstream with the returned id, which implies this is the discovery step before triggering a scan. There is no explicit statement of when to prefer this over sibling listing tools such as list_recent_scans, and no exclusions.

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