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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so 'Read-only' largely restates structured data. The description does add a little beyond that: the enumerated return fields and the note that the call executes immediately without a confirmation round-trip. It says nothing about result ordering or what happens when the list is empty/truncated.

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 returned-field list arrives in the first sentence, which is the right front-loading. The trailing '(site: ...)' and 'Through Royally: read-only, runs straight away' are largely boilerplate that repeats the annotations, but they cost only a few words.

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-parameter list tool with no output schema, naming the returned fields and confirming read-only behaviour covers the essentials. The remaining gaps (limit/pagination behaviour, search scope) are what keep it from being fully complete.

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 only 33% — only site_id is documented (via its enum description). The description does not mention `limit` (1-100) or `search` at all, so it is unclear whether search matches title, content, or category, or whether limit defaults to something. With low coverage the description should compensate, and it does not.

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 gives a specific verb and resource (list the site's patterns / reusable blocks) and even enumerates the returned fields (ID, title, status, synced flag, categories, size). It never explicitly contrasts itself with royal-mcp__wp_get_synced_pattern (the single-item read) or the create/update siblings, so an agent must infer that distinction from the names.

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?

'Read-only, runs straight away' tells the agent the call is safe and needs no approval step, which is useful context. But there is no statement of when to choose this over wp_get_synced_pattern for a single pattern, and no guidance on when to pass `search` versus listing everything.

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