wp_blocks_list

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

With no annotations, the description carries the full burden of behavioral disclosure. It hints that the output includes paths and hashes for reading and editing, but it does not explain the output structure, confirm read-only behavior, or mention pagination, depth limits, or side effects.

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 description is a single concise sentence with the core action front-loaded. It is efficient, though the second clause is terse and cryptic.

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 tool with four parameters, no annotations, and no output schema, this one-line description is insufficient. Agents are left without clarity on depth behavior, filter usage, post_type handling, or the shape of the returned block outline.

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 50%, covering ref and filter but leaving depth and post_type undocumented. The description adds no parameter-level meaning and only obliquely refers to paths and hashes, which are not parameters. It fails to compensate for the low schema coverage.

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 states a specific verb ('List') and resource ('post/page Gutenberg outline'), making the core purpose understandable. However, it does not differentiate itself from nearby siblings like wp_blocks_find or wp_blocks_get, and the phrase 'outline' is somewhat ambiguous without further context.

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?

There is no guidance about when to choose this tool over its many block-related siblings. 'Use paths to read and hashes to edit' hints at how the output might be used, but it does not provide selection criteria, exclusions, or alternatives.

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