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 fully covered. The description adds little beyond repeating 'Read-only' twice and saying it 'runs straight away' (no confirmation step), and it does mention the read-only nature plus the target site, but adds no depth on output shape or errors.

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?

Very short and front-loaded with the operation, which is good. However 'Read-only' is stated twice and '(site: demo.royalplugins.com)' duplicates the site_id enum description, so a meaningful share of 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?

For a single-resource read with full annotation coverage and no output schema, the description plus schema give an agent enough to act: the resource, the identifier source, the type enum, and that it returns markup plus block stats. Only minor gaps remain around error behavior when the id is invalid.

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%, and the schema itself explains that id comes from wp_list_block_templates, the type enum default, and the single allowed site_id. The description adds no parameter meaning beyond that, so 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?

States a specific verb and resource ('Get one block template or template part's markup and block stats'), making clear it retrieves a single template plus parsed stats. The word 'one' implicitly distinguishes it from the sibling wp_list_block_templates, but the sibling is never named explicitly.

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?

Usage is only implied — an agent can infer it should call this after listing templates to inspect a specific one. There is no explicit statement of when to prefer this over wp_list_block_templates, wp_get_block_outline, or wp_get_synced_pattern.

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