wp_create_synced_pattern

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, but it only restates the basic 'create' behavior and the dry-run capability, which is already documented in the dry_run parameter description. It does not disclose side effects, required permissions, return values, or what happens on validation failure.

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 appropriately short and front-loaded: 'Create synced pattern' leads with the core purpose, followed by the dry-run note. Every word earns its place, though more content would be needed for full usefulness.

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?

Given five parameters, no output schema, and no annotations, the two-sentence description leaves important context uncovered, such as default status behavior, expected content format, slug requirements, and what the response contains. The tool is a mutation operation with no supporting annotations, so the description is not complete enough for reliable invocation.

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 20%, so the description should compensate by explaining key parameters, but it only mentions dry-run and does not clarify title, content, slug, or status semantics. The schema provides parameter names and types, but the description adds little meaning beyond that.

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 action ('Create') on a specific resource ('synced pattern'), which is clear and distinguishable from sibling tools like wp_update_synced_pattern and wp_delete_synced_pattern by verb. However, it does not elaborate on what a synced pattern is or how it differs from related concepts like block patterns, so it is clear but minimal.

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 gives no guidance on when to use this tool versus alternatives such as wp_update_synced_pattern or wp_create_post. The only usage hint, 'Supports dry-run,' implies a pre-write validation use case but does not explain when that mode should be chosen or any prerequisites.

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