wordpress_create_reusable_blockCreate a reusable block in WordPress by providing a title and content, enabling consistent design across posts and pages.
Create a reusable block
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | ||
| content | Yes |
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It does not mention permissions, side effects, duplicate handling, content format, or return values. For a mutating operation, this is a complete lack of 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 extremely concise, but it is under-specified rather than appropriately sized. It is a single fragment that does not provide enough information to be considered well-structured or valuable.
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?
Although the tool has only two parameters and no output schema, the description is too minimal for a create operation. It does not explain what a reusable block is, what content format is expected, or any prerequisites. It is incomplete for practical use.
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 does not explain the meaning or expected format of 'title' and 'content'. While the names are somewhat self-evident, the content type (HTML, block markup, etc.) is unspecified, and the description fails to compensate for the schema's lack of detail.
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 'Create a reusable block' has a specific verb ('Create') and resource ('reusable block'), clearly distinguishing it from sibling tools like get/update/delete_reusable_block. It unambiguously states the tool's function.
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 no explicit guidance on when to use this tool versus alternatives. It does not mention related tools like wordpress_update_reusable_block or wordpress_get_reusable_blocks. Usage is only implied by the tool name and action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.