mcp_get_elementor_flat

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

No annotations are provided, so the description must carry the full burden. The description indicates the tool returns a flat list of all Elementor elements, implying a read operation. However, it does not disclose potential performance impacts, pagination behavior, or whether it respects permissions. It adds some clarity but misses important behavioral details.

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, concise sentence that effectively communicates the primary purpose. It is front-loaded and avoids unnecessary verbosity. However, it could be slightly more comprehensive without losing conciseness.

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?

The tool has no output schema and 4 parameters. The description does not hint at the response format (e.g., array of element objects), potential size of the list, or any pagination. Given the lack of annotations and output schema, the description should provide more context about what the agent can expect. This gap makes it less complete.

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?

With 100% schema description coverage, each parameter already has a clear description (id, widget_type, el_type, fields). The description adds no additional parameter-level information beyond stating the overall purpose. Baseline score of 3 is appropriate since the schema does the heavy lifting.

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's purpose: 'Get flat list of all Elementor elements on a page'. It specifies the resource (Elementor elements on a page) and the verb (Get), and distinguishes from a tree representation by noting it's 'easier to search/filter than tree'. This differentiation from sibling tools like mcp_get_elementor_build is implied.

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 provides a brief rationale for using this tool ('easier to search/filter than tree'), but does not explicitly state when to use it versus alternatives such as mcp_get_elementor_element or mcp_get_elementor_build. No when-not-to-use guidance is given, and no alternatives are named.

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