mcp_get_elementor_flat

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It conveys that the output is flat rather than nested, but says nothing about permissions, pagination, ordering, or how the 'fields'/'el_type' filters affect results, and it omits any return-shape context.

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?

A single efficient sentence with the core purpose front-loaded and the contrast parenthetical at the end. No wasted words, though it is sparse enough that brevity shades into under-specification.

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?

For a read/list tool with full schema coverage and no output schema, the description covers the essential purpose. It is thin on return shape, pagination, and filter interaction, so it is adequate but not fully complete for a five-parameter query tool.

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 description coverage is 100%, so the schema already documents all five parameters, and the description adds no syntax or format detail beyond 'on a page'. Per the coverage rule, baseline 3 is correct when 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?

States a specific verb ('Get') and resource ('flat list of all Elementor elements on a page'), and contrasts with the 'tree' form. It does not name the specific sibling (e.g., mcp_get_elementor_element or mcp_get_elementor_build), so differentiation is by shape rather than by tool name.

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 parenthetical '(easier to search/filter than tree)' implies when to prefer this tool, which is genuine usage context. However, it names no concrete alternative tool and gives no exclusions or prerequisites, leaving the agent to infer the routing.

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