mcp_get_elementor_element

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

No annotations are given, yet the description only states it 'gets' an element. It does not disclose whether the operation is safe, idempotent, or any potential side effects. As a read tool, it should at least imply no destructive impact, but this is not explicit.

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, efficient sentence. It is front-loaded with the verb and resource. However, it could be slightly more structured to include additional context without becoming verbose.

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?

Given the lack of output schema and annotations, the description is too brief. It doesn't explain what an 'Elementor element' is, how to obtain the element_id, or what 'full settings' entail. This leaves the agent without enough context for complex use cases.

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?

The input schema already describes both parameters (id and element_id) with 100% coverage. The description adds no additional semantic value beyond the schema, meeting the baseline but not exceeding it.

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 action ('Get') and the resource ('a single Elementor element') with a qualifier ('full settings'). It distinguishes from siblings like mcp_get_elementor_build or mcp_get_elementor_kit by specifying 'single' and 'full settings', though it doesn't explicitly contrast with them.

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_search_elementor or mcp_get_elementor_flat. The description lacks usage context or prerequisites.

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