wp_insert_block_pattern

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the core insertion action but does not mention whether the pattern is appended or replaces existing content, whether editing permissions are required, or what happens on failure. This is a mutation operation with no side-effect or reversibility context.

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 front-loaded sentence with no filler; the verb, resource, target, and preset examples all earn their place. It is easy for an agent to scan quickly.

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 simple two-parameter tool with an enum, the description plus schema is mostly sufficient to invoke it correctly. However, with no annotations and no output schema, it leaves moderate gaps around the insertion behavior, such as where the pattern lands, whether content is overwritten, and required permissions, so it is only minimally 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 coverage is only 50% because page_id has no description, but the tool description maps page_id to the target page/post and clarifies preset as a built-in block pattern. It adds semantic context to the undocumented parameter, even though the preset examples duplicate the schema enum.

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 (insert), a distinct resource (Gutenberg block pattern preset), and the target (a page/post), and enumerates the available presets. This makes the tool clearly distinguishable from sibling content tools like wp_update_block or wp_create_post without needing to open the schema.

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 states what the tool does but gives no guidance on when to choose it over alternatives, and no exclusions or prerequisites. An agent cannot tell whether this should be used instead of wp_update_block for existing content, wp_create_post for new posts, or Elementor insertion tools.

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