bricks_wp_create_post

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

The description discloses that it returns the new post ID and URL, but with no annotations, it does not mention default status ('draft'), permission requirements, or side effects. Adequate but not thorough.

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?

Exceptionally concise: one sentence that captures the core action and key output. No unnecessary words; front-loaded for quick understanding.

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?

Despite having 7 parameters and no output schema, the description is minimal. It omits default behavior (draft status), the need for an active site, and how parameters interact. Incomplete for a complex creation tool.

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 100% so the baseline is 3. The description adds no additional context for parameters (e.g., that tags/categories expect IDs, or that content is HTML). Schema is sufficient but description provides no extra value.

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 it creates a new WordPress post and returns ID and URL. However, it does not distinguish from siblings like bricks_create_page, which may also create posts/pages, leaving ambiguity for the agent.

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?

No guidance on when to use this tool versus alternatives (e.g., bricks_create_page for Bricks-specific pages, bricks_wp_update_post for updates). The agent must infer context from the name alone.

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