bricks_create_page

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

No annotations provided, but description implies a write operation. Does not disclose permissions, rate limits, or side effects. Adds minimal behavioral context beyond the obvious creation action.

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?

Three sentences, no fluff. First sentence states purpose clearly, second offers workflow tip, third gives specific styling recommendations. Front-loaded and efficient.

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 no output schema, description covers purpose, key workflow, and styling best practices. Missing details on return value (likely page ID) and potential prerequisites, but adequate for a straightforward creation tool with high schema coverage.

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% with descriptions for all 6 parameters. The description adds value by providing styling guidance and workflow hints that go beyond schema, enhancing understanding of how to use elements and status.

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 WordPress page with Bricks Builder data in one call, distinguishing it from separate WP page creation and data push. The verb 'Create' and resource 'WordPress page with Bricks Builder data' are specific.

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?

Provides explicit when-to-use context: combine page creation and Bricks data push. Includes best practices like calling theme styles and global classes first, preferring specific styling approaches. Lacks explicit alternatives, but the guidance is clear.

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