wp_list_blocks

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

With no annotations, the description must carry the behavioral disclosure burden. It does disclose the return format in useful detail (blockName, path, attributes preview) and the verb 'List' implies a read-only operation, but it does not mention limitations, edge cases, or any side effects. This is adequate but not rich.

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?

A single sentence that front-loads the core action and resource, then compresses the output contract into a compact list. Every word adds value, and there is no redundant filler.

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?

The tool has a single well-documented parameter and no output schema, so the description's mention of blockName, path, and attributes preview covers the return contract. It is complete enough for a simple read-only list operation, though 'path' could have been clarified further.

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 coverage is 100%, so the schema already fully documents page_id as the WordPress page or post ID. The description adds no new parameter-level meaning, but none is needed; the baseline of 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 action ('List') and a precise resource ('Gutenberg blocks on a page/post'), then specifies the exact output shape ('flat index with blockName, path, and attributes preview'). This clearly distinguishes it from sibling block-related tools like wp_update_block or wp_insert_block_pattern.

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?

The description implies the tool is for inspecting blocks within a specific page or post, but it gives no explicit guidance on when to choose this over alternatives such as wp_get_page or wp_update_block. No exclusions, prerequisites, or alternative routing are mentioned.

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