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

The annotations already declare readOnlyHint=true and idempotentHint=true; the sentence 'its server marks it read-only, so it runs straight away' largely restates that and adds only the operational note that no approval step occurs. Nothing is said about what happens with an unknown element_id, whether revision/draft state affects the result, or the shape of 'all control values'.

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?

Two short, front-loaded sentences establish the action and the inputs efficiently. The trailing 'Through Royally: its server marks it read-only, so it runs straight away' is largely redundant with the annotations and is the one sentence that does not fully earn its place.

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?

With no output schema, the description must carry the return-value burden, and it only says 'all control values' without indicating whether that is a flat control=>value map, nested responsive values, or raw _elementor_data. For a read-only getter with full schema coverage this is adequate but leaves a real gap for an agent planning downstream use.

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% and all three parameters are documented there, so the baseline is 3. The description only restates that post_id and element_id are the inputs and adds the notion of 'all control values' for the element; it does not clarify element_id format (e.g., the Elementor 7-char ID) or site_id's fixed enum value.

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 ('Returns') and a narrowly scoped resource ('the current settings for a specific element on a page'), which distinguishes it implicitly from siblings like emcp-tools-get-settings (global) and emcp-tools-get-page-structure. It never names those siblings, so the differentiation is left to inference.

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?

It tells the agent what inputs are needed ('Provide the post ID and element ID') and what comes back, which implies the usage context. There is no explicit when-to-use versus emcp-tools-get-settings, emcp-tools-find-element, or emcp-tools-get-page-structure, and no stated failure conditions.

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