mcp_get_elementor_page_settings

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

No annotations provided, so the description carries the full burden. 'Get' implies a read-only operation, but the description says nothing about permissions, whether it requires a valid Elementor page, what happens if settings are absent, or the return shape. For a zero-annotation tool this is a significant gap.

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 tight sentence with the resource front-loaded and useful parenthetical examples. No wasted words, though it is brief to the point of being sparse.

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 simple two-parameter read tool whose schema is fully documented, the description is minimally adequate. It lacks prerequisites and any hint of the settings returned, which matters since there is no output schema.

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%: 'id' is documented as 'Post/page ID' and 'site' as 'Site id (see list_sites)'. The description adds nothing beyond the schema, so the baseline 3 applies.

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 ('Elementor page-level settings') and gives concrete examples ('hide title, custom CSS'). An agent can tell it apart from siblings like mcp_get_elementor_element or mcp_get_elementor_kit by the page-level scope, though the description never explicitly names those alternatives.

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 on when to use this versus mcp_get_elementor_build, mcp_get_elementor_flat, or mcp_get_elementor_kit. No prerequisites stated (Elementor must be active, valid post/page ID required). Usage is only implied by the name.

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