mcp_get_elementor_build

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

Absent annotations, the description should fully disclose behavioral traits. It only states 'Get full Elementor page build' without mentioning aspects like performance impact, required permissions, or what happens if the post ID does not exist or is not an Elementor page.

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 a single sentence, concise and front-loaded. It efficiently conveys the core purpose without extraneous text, earning a 4.

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 good sibling differentiation, the description lacks completeness. There is no mention of return values, pagination, or behavior when fields parameter is used. The complexity of Elementor builds warrants more context, but none is provided.

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 meaning beyond the schema, which already documents the id and fields parameters. A 3 is appropriate as no extra param insight is provided.

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 retrieves the full Elementor page build, including containers, widgets, and settings tree. This verb+resource structure effectively distinguishes it from sibling Elementor tools like mcp_get_elementor_conditions or mcp_get_elementor_page_settings.

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 such as mcp_get_elementor_element or mcp_get_elementor_flat. The description lacks explicit when-to-use or when-not-to-use instructions.

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