bricks_wp_create_post

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

With no annotations, the description discloses the primary action and its return value. It falls short of disclosing side effects such as the default status of 'draft', permission requirements, or that content type depends on post_type.

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 brief and to the point, with no filler. The action is stated first and the return value added in a second sentence, both of which earn their place.

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 the rich schema covering all 8 parameters, the short description is sufficient for a creation tool. The output behavior is described (ID and URL), although it does not mention the default draft status or relationships to other creation tools.

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?

The schema covers 100% of parameters, so baseline is 3. The description does not add parameter-specific meaning beyond what the schema already provides, but the schema is sufficiently detailed to compensate.

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 'Create a new WordPress post' using a specific verb and resource. It distinguishes itself from update tools (bricks_wp_update_post) and other creation tools like bricks_create_page by the WordPress post type.

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 is provided on when to use this tool versus alternatives like bricks_create_page or bricks_wp_update_post. The usage context is implied by the name and siblings but never explicitly stated.

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