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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the description's 'Read-only' and 'read-only, runs straight away' are restatements rather than added context. It does state the return contents (block markup plus block stats), but nothing about size of markup output, site-scoping behavior, or error cases when an ID is invalid.

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?

Three short fragments, with the core purpose front-loaded, but 'Read-only.' and 'Through Royally: read-only, runs straight away.' say the same thing twice and also duplicate the annotation hints. The site note duplicates the site_id enum description, so roughly half the text is redundant.

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?

This is a simple single-record read with fully documented parameters and no output schema, and the description states what is returned. Only the lack of any guidance on alternatives or on behavior for an unknown ID keeps it from being 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 100%: both id ('Pattern ID from wp_list_synced_patterns') and the single-valued site_id enum are documented in the schema. The description adds no syntax, format, or constraint information beyond that, so the baseline 3 applies.

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: 'Get one pattern's block markup and block stats.' The singular 'one pattern' implicitly contrasts with the sibling wp_list_synced_patterns, and the schema's 'Pattern ID from wp_list_synced_patterns' confirms the pairing, but that routing is in the schema rather than the description itself.

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 in the description says when to use this tool versus wp_list_synced_patterns, wp_update_synced_pattern, or wp_get_block_outline. The only contextual note ('Read-only', 'runs straight away') describes safety, not selection conditions. An agent must infer usage purely from the parameter schema.

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