wp_blocks_list

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

No annotations are provided, so the description must disclose behavior. It only states that it lists blocks, without mentioning pagination, filtering, output structure, permissions, or side effects. The added context about reusable blocks is domain knowledge, not behavioral transparency.

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 concise (two sentences) and front-loaded with the core action. It avoids fluff and is efficient, though it could potentially be even clearer with parameter context. Still, it earns its place by clarifying the resource type.

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 6 parameters, no annotations, and no output schema, the description is incomplete. It gives domain context about reusable blocks but fails to explain pagination, filtering, statuses, sorting, or the response format. The agent would struggle to use this tool correctly without additional information.

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 0%, and the description adds no meaning to any of the 6 parameters (page, order, search, status, orderby, per_page). It neither lists nor explains them, leaving the agent entirely dependent on the schema's raw names and enums.

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 clearly states the tool lists reusable Gutenberg blocks (post type wp_block), using a specific verb (List) and resource. It distinguishes itself from sibling tools like wp_blocks_get (single block) and wp_posts_list (regular posts) by focusing on reusable blocks.

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 provides context by explaining what reusable blocks are and their purpose, implying usage for listing such blocks. However, it does not explicitly mention alternatives or when not to use this tool, so guidance is only implied rather than explicit.

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