wp_elementor_update_shortcode_content

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

With no annotations, the description carries the full disclosure burden and does so effectively by warning that writes are silently discarded. This reveals the exact failure mode an agent needs to know and prevents false confidence in apparent success.

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 sentence with the critical warning front-loaded before the mechanism. Every word earns its place, and there is no repetition of schema information or filler.

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 an experimental, disabled mutation tool with no annotations and no output schema, the description supplies the decisive fact: writes are discarded, so the tool cannot be relied upon. It does not mention an alternative or expected response, but those are secondary when the tool is currently unusable.

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 coverage is 100%, so the schema already documents both page_id and new_content, establishing a baseline of 3. The description adds no further per-parameter meaning; the _elementor_data mention indirectly clarifies what new_content affects but offers no additional syntax or constraints.

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 identifies the operation as direct writes to Elementor's _elementor_data via WordPress REST, clearly implying this is the update path for Elementor shortcode content. It is specific about the mechanism and current status, though it does not explicitly compare itself to sibling tools such as wp_elementor_get_shortcode_content.

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 explicitly states 'currently unavailable,' giving an unambiguous do-not-use signal. It does not name an alternative, but for a disabled tool the core guidance is to avoid invocation, which is clearly communicated.

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