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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value beyond that by promising immediate execution with no approval step ('runs straight away') and by stating which schedule fields come back. It stops short of describing response shape or error behavior, but that is a modest gap given the annotation coverage.

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 purpose and returned fields are front-loaded in the first sentence and the parenthetical is compact. The phrase 'Read-only. ... read-only' is mildly redundant and the 'Through Royally' fragment is stylistically noisy, but nothing is padded or wasteful.

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-required-param read tool with rich annotations and no output schema, the description tells the agent what it fetches and what fields to expect. Enough to call it correctly; only the sibling-disambiguation would improve it.

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 optional site_id parameter with 100% schema description coverage and a single enum value, so the schema already does the explanatory work. The description's '(site: demo.royalplugins.com)' merely echoes the schema's own site hint without adding format or multi-site selection guidance. Baseline 3 applies when schema coverage is complete.

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 a specific verb and resource ('Read the current UpdraftPlus backup schedule') and enumerates exactly what it returns (files interval, database interval, retention counts, next scheduled run). That makes the tool's intent unambiguous against the many other read tools. It does not, however, distinguish itself from near-siblings such as royal-mcp__updraftplus_list_backups or royal-mcp__sv_get_schedules, so an agent must infer the boundary.

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?

Nothing states when to pick this over updraftplus_list_backups (backup contents) or sv_get_schedules (other backup plugin's schedules). The 'read-only, runs straight away' note describes execution behavior rather than selection criteria, and no prerequisites or exclusions are given.

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