bricks_elementor_to_bricks

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

With no annotations provided, the description carries full burden. It discloses the tool is a conversion-only operation (no writing), returns a structured output (array + coverage report), and does not modify WordPress. This provides adequate transparency, though it could explicitly state idempotency or lack of side effects.

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 (3 sentences) and well-structured: purpose, input specification, output description, and explicit non-action. Every sentence adds value with no redundancy.

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, the description adequately explains outputs (Bricks element array + coverage report). It covers inputs, process, and expected results. However, it could mention the coverage report's structure or that elements are native Bricks structures, but this is minor given the tool's simplicity.

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 both parameters described. The description adds context: json can be 'export wrapper or raw array', file_path is 'absolute path'. This enriches the schema definitions, making it easier for an agent to decide which parameter to use.

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 the tool converts Elementor page/template to Bricks element array, specifying input format (Elementor JSON export) and output (Bricks element array + coverage report). It distinguishes itself from siblings like bricks_html_to_bricks or bricks_import_template by focusing on Elementor conversion.

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 explicitly says when to use (to convert Elementor content) and importantly states what it does NOT do: 'Does NOT write to WordPress: review the output, then push with bricks_update_page or bricks_import_page.' This gives clear guidance on next steps and alternative tools.

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