Publish a page to live, cascading updates to shared global sections so changes apply everywhere consistently.
Compile the draft into the live page. PUBLISH CASCADES: a page sharing a global section with others republishes them too, because a header edited once must not go live on one page and stay stale on the rest.
| Name | Required | Description | Default |
|---|---|---|---|
| dry_run | No | ||
| page_id | Yes | ||
| site_id | No |
Changes observed during successful MCP inspections.
v0.12.0Input schema / requiredPrevious value: -[
- "site_id",
- "page_id"
-]New value: +[
+ "page_id"
+]v0.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructive and idempotent behavior; the description adds valuable transparency by explicitly calling out the cascading republish side effect.
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 and front-loaded, with no redundant wording; the cascade note is purposeful and directly relevant to the tool's behavior.
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?
The description covers the main purpose and an important side effect, but it omits parameter semantics, especially dry_run and site_id, so it is not fully complete for 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 descriptions are absent and the description does not explain page_id, site_id, or dry_run, leaving parameter meaning mostly to inference from names.
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?
States a specific action ('Compile the draft into the live page') with a clear subject and verb, and the cascade explanation helps distinguish it from related sibling tools.
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 intended use is implied by the description, but it does not explicitly mention when to prefer this tool over alternatives or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.