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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real domain context beyond that: 48 hours of hourly runs, paused plugin updates, and the fact that it reports expected and unexpected changes.

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 sentences: the first front-loads the concept and constraints, the second enumerates return fields. Dense but every clause maps to actual behavior; no wasted preamble.

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?

No output schema exists, so the description's enumeration of returned facts (availability, on/off, until when, changes seen, monitors, runs, past sessions) usefully compensates. With annotations covering safety, an agent has enough to call it 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?

There is a single required siteId parameter and schema coverage is 100%, so the schema already documents it fully. The description adds no parameter-level meaning, making the baseline 3 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 names the specific resource (quarantine mode) and its domain well, making it clear this tool retrieves quarantine state. It is distinguishable from write siblings like start_quarantine and extend_quarantine by the list of read-only facts it returns, though it never uses an explicit retrieval verb.

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 states a domain constraint (WordPress, paid plans) but gives no when-to-use guidance and never references alternatives such as start_quarantine, extend_quarantine, or list_runs. An agent must infer the call context on its own.

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